2006-03-20 22:25:11 -07:00
|
|
|
obj-$(CONFIG_IP_DCCP) += dccp.o dccp_ipv4.o
|
2005-08-09 21:14:34 -06:00
|
|
|
|
2006-03-20 22:25:11 -07:00
|
|
|
dccp-y := ccid.o feat.o input.o minisocks.o options.o output.o proto.o timer.o
|
|
|
|
|
|
|
|
|
|
dccp_ipv4-y := ipv4.o
|
2005-08-09 21:14:34 -06:00
|
|
|
|
2006-11-14 06:50:36 -07:00
|
|
|
# build dccp_ipv6 as module whenever either IPv6 or DCCP is a module
|
|
|
|
|
obj-$(subst y,$(CONFIG_IP_DCCP),$(CONFIG_IPV6)) += dccp_ipv6.o
|
|
|
|
|
dccp_ipv6-y := ipv6.o
|
|
|
|
|
|
2005-09-18 01:17:51 -06:00
|
|
|
dccp-$(CONFIG_IP_DCCP_ACKVEC) += ackvec.o
|
|
|
|
|
|
[INET_DIAG]: Move the tcp_diag interface to the proper place
With this the previous setup is back, i.e. tcp_diag can be built as a module,
as dccp_diag and both share the infrastructure available in inet_diag.
If one selects CONFIG_INET_DIAG as module CONFIG_INET_TCP_DIAG will also be
built as a module, as will CONFIG_INET_DCCP_DIAG, if CONFIG_IP_DCCP was
selected static or as a module, if CONFIG_INET_DIAG is y, being statically
linked CONFIG_INET_TCP_DIAG will follow suit and CONFIG_INET_DCCP_DIAG will be
built in the same manner as CONFIG_IP_DCCP.
Now to aim at UDP, converting it to use inet_hashinfo, so that we can use
iproute2 for UDP sockets as well.
Ah, just to show an example of this new infrastructure working for DCCP :-)
[root@qemu ~]# ./ss -dane
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 0 *:5001 *:* ino:942 sk:cfd503a0
ESTAB 0 0 127.0.0.1:5001 127.0.0.1:32770 ino:943 sk:cfd50a60
ESTAB 0 0 127.0.0.1:32770 127.0.0.1:5001 ino:947 sk:cfd50700
TIME-WAIT 0 0 127.0.0.1:32769 127.0.0.1:5001 timer:(timewait,3.430ms,0) ino:0 sk:cf209620
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2005-08-12 09:59:17 -06:00
|
|
|
obj-$(CONFIG_INET_DCCP_DIAG) += dccp_diag.o
|
2006-09-21 20:28:01 -06:00
|
|
|
obj-$(CONFIG_NET_DCCPPROBE) += dccp_probe.o
|
2005-08-12 06:27:49 -06:00
|
|
|
|
2006-03-20 20:25:02 -07:00
|
|
|
dccp-$(CONFIG_SYSCTL) += sysctl.o
|
|
|
|
|
|
2005-08-12 06:27:49 -06:00
|
|
|
dccp_diag-y := diag.o
|
2006-09-21 20:28:01 -06:00
|
|
|
dccp_probe-y := probe.o
|
[INET_DIAG]: Move the tcp_diag interface to the proper place
With this the previous setup is back, i.e. tcp_diag can be built as a module,
as dccp_diag and both share the infrastructure available in inet_diag.
If one selects CONFIG_INET_DIAG as module CONFIG_INET_TCP_DIAG will also be
built as a module, as will CONFIG_INET_DCCP_DIAG, if CONFIG_IP_DCCP was
selected static or as a module, if CONFIG_INET_DIAG is y, being statically
linked CONFIG_INET_TCP_DIAG will follow suit and CONFIG_INET_DCCP_DIAG will be
built in the same manner as CONFIG_IP_DCCP.
Now to aim at UDP, converting it to use inet_hashinfo, so that we can use
iproute2 for UDP sockets as well.
Ah, just to show an example of this new infrastructure working for DCCP :-)
[root@qemu ~]# ./ss -dane
State Recv-Q Send-Q Local Address:Port Peer Address:Port
LISTEN 0 0 *:5001 *:* ino:942 sk:cfd503a0
ESTAB 0 0 127.0.0.1:5001 127.0.0.1:32770 ino:943 sk:cfd50a60
ESTAB 0 0 127.0.0.1:32770 127.0.0.1:5001 ino:947 sk:cfd50700
TIME-WAIT 0 0 127.0.0.1:32769 127.0.0.1:5001 timer:(timewait,3.430ms,0) ino:0 sk:cf209620
Signed-off-by: Arnaldo Carvalho de Melo <acme@mandriva.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
2005-08-12 09:59:17 -06:00
|
|
|
|
|
|
|
|
obj-y += ccids/
|
