| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
| |
The shm_du_map is renamed to shm_rdrbuff to reflect the Random
Deletion Ringbuffer used in the implementation. The close_on_exit call
is removed and SDUs are cleaned up by the application in the ap_fini()
call. This required a non-blocking peek() operation in the shm_ap_rbuff.
Some initial implementation for future support of qos cubes has been
added to the shm_rdrbuff.
|
|
|
|
| |
IPCPs will report their pid on shutdown for faster debugging.
|
|
|
|
| |
Destruction of the object in the reply stage was unsafe.
|
|
|
|
| |
This removes the ret value which was not being set correctly.
|
|\
| |
| |
| | |
Fix locks
|
| | |
|
|\|
| |
| |
| | |
ipcpd: Revised locking
|
| |
| |
| |
| |
| |
| | |
The state lock was reverted to an rwlock to avoid interference of
management functions with the fast path. IPCPs now close without
calling unsafe functions in the signal handler.
|
|\ \
| |/
|/|
| | |
ipcpd: normal: Add initial steps for N+1 flow allocation
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds the initial framework for flow allocation between two N+1
endpoints. The FMGR will receive flow allocation requests and will
create a connection as a result, addressed to the right address, it
will also pass a flow allocation message to this address. Upon receipt
on the other side, the FMGR will be receive a flow allocation message
and a pointer to a new connection. The FMGR can then accept or destroy
the connection. This commit also introduces the RMT function, which is
needed by the FRCT to forward its SDUs on the right file descriptor.
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The complete data model inside the IRMd has been restructured. The
bind operation was revised to allow binding of AP and AP instances and
register those names with different DIFs (see "irm bind" for details).
Server applications require to call ap_init with a server name
argument, client application that do not the be reachable over any DIF
can call ap_init(NULL). Calling ap_init for a client with a specified
name will not have adverse consequences for the application, but will
consume unnecessary resources in the IRMd.
Application servers can now be started at any point after the IRMd has
been started. Starting servers, binding AP names and registering names in
DIFs can be performed in any order that does not defy temporal logic.
Supports naming instances by their pid. In case of IPCP Instances
created with the IRM tool, the name assigned during "irm ipcp create"
can be used.
All the changes required updates in the tools.
|
|
|
|
|
|
|
|
| |
This adds a condition variable with a timeout to the CDAP request so
that we can respond correctly to the answer from the remote. It also
adds a timeout to the condition variable waiting on completion of
enrollment. Furthermore, for every CDAP callback a new thread is now
spawned, to avoid deadlocking in case a callback is stuck.
|
|
|
|
|
|
|
| |
Previously it was up to the admin to choose whether or not to enable
DDNS. Now the build just checks if the executables can be found, and
if they are available DDNS functionality is enabled, else it is
disabled.
|
|
|
|
|
| |
Calling api_bind during bootstrap caused the IRMd to lock up.
api_bind is now called after the normal completes bootstrapping.
|
|
|
|
|
|
|
| |
This adds a condition variable to the IPCP state, so that upon state
changes any listeners to state changes can be notified. It also
replaces the read/write lock with a mutex in order to be able to do
so.
|
|
|
|
|
| |
conf->dif_name was not copied from the dif_config gpb message.
Fixes some logs.
|
| |
|
|
|
|
|
| |
Now the correct max length of an SDU is checked upon writing a frame,
as well as on receiving it.
|
|\
| |
| |
| | |
lib, irmd: Bind AP instances to AP_subsets
|
| |
| |
| |
| |
| |
| |
| | |
This call will allow grouping AP instances of a certain AP together
which are configured identically. Adds the bind operation to dev and
updates the applications to make use of this call. Flow_alloc is now
only called with the pid and doesn't send the apn anymore.
|
| |
| |
| |
| |
| |
| | |
This adds the MSG_DONTWAIT flag to the send function of the
shim-eth-llc, when using PF_PACKET. Previously the send would return
only after the frame was sent, resulting in poor performance.
|
|/
|
|
|
|
| |
This will add a timeout to the socket so that a process won't be
blocked by the actions of the process with which it is communicating
over the socket.
|
|\
| |
| |
| | |
ipcp, irmd, lib: Notify IRMd upon IPCP initialization
|
| |
| |
| |
| |
| |
| | |
This will notify the IRMd when the IPCP is initialized and ready to
receive messages. Previously a bootstrap could fail since the IPCP was
not listening to the socket yet.
|
|/
|
|
|
| |
A lock was not being taken to check the state, but then it was
released if the state was not IPCP_NULL, resulting in a segfault.
|
| |
|
|
|
|
|
|
| |
This changes the amount of time the shim-eth-llc will hold the IPCP
state lock when sending and receiving frames. Before it was holding
the lock for too long.
|
| |
|
|
|
|
|
|
| |
This adds the functionality of exchanging the static DIF information
between 2 DIF members. After exchange the enrollment is stopped, and
the IPCP that initiated enrollment transitions to the enrolled state.
|
|
|
|
| |
The entry from the ringbuffer was never freed, causing memleak per SDU.
|
|
|
|
|
| |
When a flow was in FLOW_ALLOCATED state, it would not change to NULL
state and irm_flow_destroy would hang forever.
|
|
|
|
| |
ipcp-data was not correctly destroyed.
|
|
|
|
| |
The cleanup was trying to close a pointer to the file descriptor.
|
|
|
|
|
|
|
|
|
| |
Blocking I/O now uses condition variables in the shared memory instead
of busy waiting. Timeouts can be specified. This requires the size of
the rbuffs and du_map to be the same, to guarantee that when the
shm_du_map is not full, the ap_rbuffs can't be full either.
Added the timeout option to the flow for future use.
|
|\
| |
| |
| | |
shim-eth-llc: Fix for bad drivers
|
| |
| |
| |
| |
| |
| |
| |
| | |
It seems like drivers are setting the Ethernet length field wrong when
sending an LLC message. The LLC shim now writes the payload length in
the frame to circumvent the wrong information from the driver.
Also fixes deallocation.
|
|\ \
| |/
|/|
| | |
Be enrolment
|
| |
| |
| |
| |
| |
| |
| | |
This will add more functionality for enrolling two normal IPCPs with
each other. Some bugs were fixed in CDAP. Now on enrolling, an IPCP
will send a START message to the other IPCP. Next step is syncing the
RIBs.
|
| |\ |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This provides the normal IPCP with bootstrapping and the initial steps
for enrollment. Next step is actually reacting to an enrollment
request and sending the data transfer constants.
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Various portability fixes for FreeBSD. POSIX requires shm file names
to start with a "/" to be portable. lseek(2) can be undefined on
POSIX shm, replaced with ftruncate(2). IRMd check on existing lockfile
more portable.
FreeBSD 11.0 is preferred as it natively supports robust mutexes.
Full working LLC implementation pending.
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
Upon receipt of a frame, the minimum of the length reported in the
frame and the frame length reported by kernel is taken. Some device
drivers change the length in the frame. Some others add padding,
making the length reported by the kernel too high. This is a lousy
workaround to make it work on as many systems as possible.
|
|/
|
|
|
|
| |
The protobuf include directory was not being correctly handed to the
compiler when building. Now the include directory is added
project-wide. And the protobuf package is searched for only once.
|
|
|
|
|
|
| |
This adds the main loop to the normal IPCP, just like it is present in
the shim IPCPs. So in essence, the normal IPCP now reacts to all
operations from ipcp.h.
|
|
|
|
|
|
|
|
|
| |
This adds the intial implementation of establishing management N-1
flows between normal IPCPs. On calling fmgr_mgmt_flow, a management
flow will be setup to a certain destination IPCP. After flow
allocation, the fd is handed to the RIB manager. The flow manager also
listens for incoming flow requests. In case they are management flows,
they are handed to the RIB manager, otherwise to the FRCT.
|
|
|
|
|
|
|
|
|
| |
This adds the initial headers for the normal IPCP. The normal IPCP
consists of 3 main components:
* The flow manager, in charge of managing N and N-1 flows.
* The RIB manager, in charge of managing the RIB
* FRCT: The flow and retransmission control task
|
|
|
|
|
|
| |
This removes the parameter N-1 DIF from the enroll operation. IPCPs
should just allocate a flow to a DIF name and let the N-1 DIF resolve
it.
|