netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: linux lover <linux_lover2004@yahoo.com>
To: acme@conectiva.com.br
Cc: netdev@oss.sgi.com
Subject: Re: Why skbuff.h different for 2.4 and 2.6 kernels?
Date: Mon, 11 Apr 2005 18:26:13 -0700 (PDT)	[thread overview]
Message-ID: <20050412012614.69495.qmail@web52209.mail.yahoo.com> (raw)
In-Reply-To: 6667

Hello,
        Thanks for reply. Can you please tell me about
my second question?
      2)But Why header structures for ipcomp, eh,
esp(IPSEC) not included in skbuff.h?
 
regards,
linux_lover.

--- Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
wrote:
> 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
> 


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/

             reply	other threads:[~2005-04-12  1:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12  1:26 linux lover [this message]
2005-04-12  1:56 ` 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  2:13 linux lover
2005-04-11 16:37 linux lover
2005-04-11 21:01 ` Arnaldo Carvalho de Melo

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=20050412012614.69495.qmail@web52209.mail.yahoo.com \
    --to=linux_lover2004@yahoo.com \
    --cc=acme@conectiva.com.br \
    --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).