From: linux lover <linux_lover2004@yahoo.com>
To: netdev@oss.sgi.com
Subject: Why skbuff.h different for 2.4 and 2.6 kernels?
Date: Mon, 11 Apr 2005 09:37:52 -0700 (PDT) [thread overview]
Message-ID: <20050411163753.20149.qmail@web52210.mail.yahoo.com> (raw)
hello,
1) In 2.4 kernel series skbuff.h has following unions
for each TCP/IP layer.
/*Transport Layer*/
union
{
struct tcphdr *th;
struct udphdr *uh;
struct icmphdr *icmph;
struct igmphdr *igmph;
struct iphdr *ipiph;
struct spxhdr *spxh;
unsigned char *raw;
} h;
/* Network layer header */
union
{
struct iphdr *iph;
struct ipv6hdr *ipv6h;
struct arphdr *arph;
struct ipxhdr *ipxh;
unsigned char *raw;
} nh;
/* Link layer header */
union
{
struct ethhdr *ethernet;
unsigned char *raw;
} mac;
AND In 2.6 kernel series skbuff.h has following unions
for each TCP/IP layer.
union {
struct tcphdr *th;
struct udphdr *uh;
struct icmphdr *icmph;
struct igmphdr *igmph;
struct iphdr *ipiph;
struct ipv6hdr *ipv6h;
unsigned char *raw;
} h;
union {
struct iphdr *iph;
struct ipv6hdr *ipv6h;
struct arphdr *arph;
unsigned char *raw;
} nh;
union {
unsigned char *raw;
} mac;
why mac union in 2.6 not have ethernet header? Also
spxhdr and ipxhdr structures are removed from nh and h
unions.
2) Why header structures for ipcomp,eh,esp(IPSEC) not
included in skbuff.h?
Then how can skbuff adds/removes those headers in
skbuff?
regards,
linux_lover
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next reply other threads:[~2005-04-11 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 16:37 linux lover [this message]
2005-04-11 21:01 ` Why skbuff.h different for 2.4 and 2.6 kernels? Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2005-04-12 1:26 linux lover
2005-04-12 1:56 ` Arnaldo Carvalho de Melo
2005-04-12 2:13 linux lover
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050411163753.20149.qmail@web52210.mail.yahoo.com \
--to=linux_lover2004@yahoo.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).