mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Analysing UDP packet building code in 2.6.10 kernel
@ 2005-01-16 13:11 linux lover
  0 siblings, 0 replies; only message in thread
From: linux lover @ 2005-01-16 13:11 UTC (permalink / raw)
  To: linux-net; +Cc: linux-kernel


Hello all,
         I am knowing all 2.4 kernel network stack
packet buildup procedure. Now i am trying to analysing
same in
2.6.10 kernel. What i found is many changes to 2.6
kernel compare to 2.4. Theres is no ip_build_xmit
instead thers a new function that is
ip_append_data. What i want to know is from udp.c
file. Theres a udp protocol structure is defined
struct proto udp_prot = {
 	.name =		"UDP",
	.owner =	THIS_MODULE,
	.close =	udp_close,
	.connect =	ip4_datagram_connect,
	.disconnect =	udp_disconnect,
	.ioctl =	udp_ioctl,
	.destroy =	udp_destroy_sock,
	.setsockopt =	udp_setsockopt,
	.getsockopt =	udp_getsockopt,
	.sendmsg =	udp_sendmsg,
	.recvmsg =	udp_recvmsg,
	.sendpage =	udp_sendpage,
	.backlog_rcv =	udp_queue_rcv_skb,
	.hash =		udp_v4_hash,
	.unhash =	udp_v4_unhash,
	.get_port =	udp_v4_get_port,
	.slab_obj_size = sizeof(struct udp_sock),
};

I want to know for what purpose udp_sendpage is used
also whats significance of . in structure members?
Also why .slab_obj_size = sizeof(struct udp_sock)
defined in udp_prot?
Also where's packet size/space is allocated for UDP
packet?
Please help me to analyze code.
Thanks in advance.
linux_lover.



		
__________________________________ 
Do you Yahoo!? 
Take Yahoo! Mail with you! Get it on your mobile phone. 
http://mobile.yahoo.com/maildemo 

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2005-01-16 13:11 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-01-16 13:11 Analysing UDP packet building code in 2.6.10 kernel linux lover

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®