Llk QA - Revision history

Tmcnulty at 06:20, 18 February 2006

2006-02-18T06:20:43Z

← Older revision		Revision as of 06:20, 18 February 2006
Line 200:		Line 200:

	[Herbert pp. 508-516]		[Herbert pp. 508-516]

			==tcp_read_sock==
			/*
			* This routine provides an alternative to tcp_recvmsg() for routines
			* that would like to handle copying from skbuffs directly in 'sendfile'
			* fashion. */
			tcp.c


	==udp_rcv==		==udp_rcv==

2006-02-18T05:25:42Z

← Older revision		Revision as of 05:25, 18 February 2006
Line 183:		Line 183:

	==tcp_data_queue==		==tcp_data_queue==
	"queues up data in the socket's normal receive queue". "puts segments that are out of order on the <code>out_of_order_queue</code>.		"queues up data in the socket's normal receive queue." "puts segments that are out of order on the <code>out_of_order_queue</code>."

	[Herbert pp. 501]		[Herbert pp. 501]

2006-02-18T05:25:11Z

← Older revision		Revision as of 05:25, 18 February 2006
Line 182:		Line 182:
	[Herbert pp. 493-501 , diagram pg. 494]		[Herbert pp. 493-501 , diagram pg. 494]

			==tcp_data_queue==
			"queues up data in the socket's normal receive queue". "puts segments that are out of order on the <code>out_of_order_queue</code>.

			[Herbert pp. 501]

	==tcp_recvmsg==		==tcp_recvmsg==

2006-02-18T04:24:37Z

tcp_rcvmsg

2006-01-13T21:38:13Z

Linux 2.6 TCP/IP Send Stack

← Older revision		Revision as of 21:38, 13 January 2006
Line 271:		Line 271:

	==ip_finish_output2==		==ip_finish_output2==
			calls dst->output or hh->hh_output, which are both function pointers to dev_queue_xmit

	ip_output.c		ip_output.c

	==~~???~~==		==dev_queue_xmit==
			dev.c

			cf. Herbert pp. 107-110

	==hard_start_xmit==		==hard_start_xmit==
	~~this might be called~~ by ~~the~~ driver ~~(i.e.,~~ we ~~may not be able to trace the full path to this point)~~		member of net_device struct (implemented by each network driver); see how we hook into it in ip_output.c
	ip_output.c
			cf. Herbert p. 100

2005-12-30T03:35:23Z

← Older revision		Revision as of 03:35, 30 December 2005
Line 271:		Line 271:

	==ip_finish_output2==		==ip_finish_output2==
			ip_output.c

			==???==

			==hard_start_xmit==
			this might be called by the driver (i.e., we may not be able to trace the full path to this point)
	ip_output.c		ip_output.c

2005-12-30T03:30:05Z

@@ Line 1: / Line 1: @@
-Linux 2.6 TCP/IP Receive Stack
+=Linux 2.6 TCP/IP Receive Stack=
 Todo for this doc:
@@ Line 218: / Line 218: @@
 [Herbert pp. 467-470]

2005-12-14T18:46:02Z

← Older revision		Revision as of 18:46, 14 December 2005
Line 1:		Line 1:
	Linux 2.6 TCP/IP Receive Stack		Linux 2.6 TCP/IP Receive Stack

			Todo for this doc:
			*finish socket functions
			*not all of our current timer points

	==Before process_backlog==		==Before process_backlog==

2005-12-14T17:23:53Z

udp_recvmsg

← Older revision		Revision as of 17:23, 14 December 2005
Line 210:		Line 210:

	==udp_recvmsg==		==udp_recvmsg==

			When receiving UDP data, the socket calls the UDP socket receive function, udp_recvmsg. This function checks for socket errors on the error message queue, dequeues packets from the socket's receive queue, and calls skb_copy_datagram_iovec to copy the datagram into the user's buffer. This may be the best place for TPR_UDP_END and TPR_SOCKET_START.

	[Herbert pp. 467-470]		[Herbert pp. 467-470]

2005-12-14T17:17:58Z

udp_sendmsg