| 
									
										
										
										
											2005-08-09 20:14:34 -07:00
										 |  |  | menu "DCCP Configuration (EXPERIMENTAL)" | 
					
						
							|  |  |  | 	depends on INET && EXPERIMENTAL | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | config IP_DCCP | 
					
						
							|  |  |  | 	tristate "The DCCP Protocol (EXPERIMENTAL)" | 
					
						
							|  |  |  | 	---help--- | 
					
						
							|  |  |  | 	  Datagram Congestion Control Protocol | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	  From draft-ietf-dccp-spec-11 <http://www.icir.org/kohler/dcp/draft-ietf-dccp-spec-11.txt>. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	  The Datagram Congestion Control Protocol (DCCP) is a transport | 
					
						
							|  |  |  | 	  protocol that implements bidirectional, unicast connections of | 
					
						
							|  |  |  | 	  congestion-controlled, unreliable datagrams. It should be suitable | 
					
						
							|  |  |  | 	  for use by applications such as streaming media, Internet telephony, | 
					
						
							|  |  |  | 	  and on-line games | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	  To compile this protocol support as a module, choose M here: the | 
					
						
							|  |  |  | 	  module will be called dccp. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	  If in doubt, say N. | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
											  
											
												[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 12:59:17 -03:00
										 |  |  | config INET_DCCP_DIAG | 
					
						
							|  |  |  | 	depends on IP_DCCP && INET_DIAG | 
					
						
							|  |  |  | 	def_tristate y if (IP_DCCP = y && INET_DIAG = y) | 
					
						
							| 
									
										
										
										
											2005-08-12 09:27:49 -03:00
										 |  |  | 	def_tristate m | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2005-08-09 20:14:34 -07:00
										 |  |  | source "net/dccp/ccids/Kconfig" | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2005-08-13 20:35:39 -03:00
										 |  |  | menu "DCCP Kernel Hacking" | 
					
						
							| 
									
										
										
										
											2005-08-27 02:35:30 -03:00
										 |  |  | 	depends on IP_DCCP && DEBUG_KERNEL=y | 
					
						
							| 
									
										
										
										
											2005-08-13 20:35:39 -03:00
										 |  |  | 
 | 
					
						
							|  |  |  | config IP_DCCP_DEBUG | 
					
						
							|  |  |  | 	bool "DCCP debug messages" | 
					
						
							|  |  |  | 	---help--- | 
					
						
							|  |  |  | 	  Only use this if you're hacking DCCP. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	  Just say N. | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | config IP_DCCP_UNLOAD_HACK | 
					
						
							| 
									
										
										
										
											2005-08-27 02:35:30 -03:00
										 |  |  | 	depends on IP_DCCP=m && IP_DCCP_CCID3=m | 
					
						
							| 
									
										
										
										
											2005-08-13 20:35:39 -03:00
										 |  |  | 	bool "DCCP control sock unload hack" | 
					
						
							|  |  |  | 	---help--- | 
					
						
							|  |  |  | 	  Enable this to be able to unload the dccp module when the it | 
					
						
							|  |  |  | 	  has only one refcount held, the control sock one. Just execute | 
					
						
							|  |  |  | 	  "rmmod dccp_ccid3 dccp" | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	  Just say N. | 
					
						
							|  |  |  | endmenu | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2005-08-09 20:14:34 -07:00
										 |  |  | endmenu |