2006-01-03 02:04:38 +08:00
|
|
|
#
|
|
|
|
|
# Makefile for the Linux TIPC layer
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
obj-$(CONFIG_TIPC) := tipc.o
|
|
|
|
|
|
2011-01-01 02:59:19 +08:00
|
|
|
tipc-y += addr.o bcast.o bearer.o config.o \
|
2014-05-05 08:56:18 +08:00
|
|
|
core.o link.o discover.o msg.o \
|
2006-01-03 02:04:38 +08:00
|
|
|
name_distr.o subscr.o name_table.o net.o \
|
2014-08-23 06:09:19 +08:00
|
|
|
netlink.o node.o node_subscr.o \
|
tipc: introduce new TIPC server infrastructure
TIPC has two internal servers, one providing a subscription
service for topology events, and another providing the
configuration interface. These servers have previously been running
in BH context, accessing the TIPC-port (aka native) API directly.
Apart from these servers, even the TIPC socket implementation is
partially built on this API.
As this API may simultaneously be called via different paths and in
different contexts, a complex and costly lock policiy is required
in order to protect TIPC internal resources.
To eliminate the need for this complex lock policiy, we introduce
a new, generic service API that uses kernel sockets for message
passing instead of the native API. Once the toplogy and configuration
servers are converted to use this new service, all code pertaining
to the native API can be removed. This entails a significant
reduction in code amount and complexity, and opens up for a complete
rework of the locking policy in TIPC.
The new service also solves another problem:
As the current topology server works in BH context, it cannot easily
be blocked when sending of events fails due to congestion. In such
cases events may have to be silently dropped, something that is
unacceptable. Therefore, the new service keeps a dedicated outbound
queue receiving messages from BH context. Once messages are
inserted into this queue, we will immediately schedule a work from a
special workqueue. This way, messages/events from the topology server
are in reality sent in process context, and the server can block
if necessary.
Analogously, there is a new workqueue for receiving messages. Once a
notification about an arriving message is received in BH context, we
schedule a work from the receive workqueue to do the job of
receiving the message in process context.
As both sending and receive messages are now finished in processes,
subscribed events cannot be dropped any more.
As of this commit, this new server infrastructure is built, but
not actually yet called by the existing TIPC code, but since the
conversion changes required in order to use it are significant,
the addition is kept here as a separate commit.
Signed-off-by: Ying Xue <ying.xue@windriver.com>
Signed-off-by: Jon Maloy <jon.maloy@ericsson.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2013-06-17 22:54:39 +08:00
|
|
|
socket.o log.o eth_media.o server.o
|
2013-04-17 14:18:28 +08:00
|
|
|
|
|
|
|
|
tipc-$(CONFIG_TIPC_MEDIA_IB) += ib_media.o
|
2013-06-17 22:54:37 +08:00
|
|
|
tipc-$(CONFIG_SYSCTL) += sysctl.o
|