[Top] [All Lists]

Re: Why skbuff.h different for 2.4 and 2.6 kernels?

To: acme@xxxxxxxxxxxxxxxx
Subject: Re: Why skbuff.h different for 2.4 and 2.6 kernels?
From: linux lover <linux_lover2004@xxxxxxxxx>
Date: Mon, 11 Apr 2005 19:13:57 -0700 (PDT)
Cc: netdev@xxxxxxxxxxx
Comment: DomainKeys? See
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024;; b=lpzyKY0yH9QlkUKNvAKFe4uzH0lOgqXF31CCrIb+4mxpMhXvm+OfvD4DAAiEZD1VmyIOfp7pYBe8LJnPxAPJiTGvZmJQpFvHt8WktwzxdmuWgLyoXATVsvYg0QPYaDiP8UI/7dQuxVfVv/+kHrM7irlZJaJCYcCKuX63jDPr864= ;
In-reply-to: 6667
Sender: netdev-bounce@xxxxxxxxxxx
--- Arnaldo Carvalho de Melo <arnaldo.melo@xxxxxxxxx>
> On Apr 11, 2005 10:26 PM, linux lover

            Sorry if my questions are stupid but again
have one question when skbuff.h is implemeted as
     void *transport_header;
        void *network_header;
        void *link_header;
            Then how say ESP packet can be constructed
in network stack. ESP has structure as 
       New IP header + ESP header + IP header +
TCP/UDP header + ESP trailer + ESP auth. header
           Does it then remains only with playing
skbuff by using skb_push and skb_pull in ESP packet
processing once skbuff.h will change?
Please kindly correct me to understand this.

 <linux_lover2004@xxxxxxxxx> wrote:
> > 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?
> I thought I have answered this, the reason to have
> the layer pointers in skb
> be void is that skb is core/generic infrastructure,
> it should not have any kind
> of protocol specific structures/information in it.
> - Arnaldo

Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!

<Prev in Thread] Current Thread [Next in Thread>