Analysing UDP packet building code in 2.6.10 kernel

From: linux lover
Date: Sun Jan 16 2005 - 08:12:58 EST



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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/