From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: linux lover <linux_lover2004@yahoo.com>
Cc: netdev@oss.sgi.com
Subject: Re: Why skbuff.h different for 2.4 and 2.6 kernels?
Date: Mon, 11 Apr 2005 18:01:04 -0300 [thread overview]
Message-ID: <39e6f6c705041114012e5a9ebe@mail.gmail.com> (raw)
In-Reply-To: <20050411163753.20149.qmail@web52210.mail.yahoo.com>
On Apr 11, 2005 1:37 PM, linux lover <linux_lover2004@yahoo.com> wrote:
> hello,
> 1) In 2.4 kernel series skbuff.h has following unions
> for each TCP/IP layer.
> 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.
Work in progress, the ultimate goal is to get rid of all of these unions and
have just:
void *transport_header;
void *network_header;
void *link_header;
So just set mac.raw directly and cast it to the desired type.
- Arnaldo
next prev parent reply other threads:[~2005-04-11 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 16:37 Why skbuff.h different for 2.4 and 2.6 kernels? linux lover
2005-04-11 21:01 ` Arnaldo Carvalho de Melo [this message]
-- 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=39e6f6c705041114012e5a9ebe@mail.gmail.com \
--to=arnaldo.melo@gmail.com \
--cc=acme@conectiva.com.br \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.