From: rahul b jain cs student <rbj2@oak.njit.edu>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sk_buff structure
Date: Tue, 22 Jun 2004 19:03:22 -0400 (EDT) [thread overview]
Message-ID: <Pine.GSO.4.58.0406221855490.15759@chrome.njit.edu> (raw)
In-Reply-To: <20040622212403.21346.qmail@lwn.net>
Thanks for the pointer. It was very helpful. Need to clarify a few more
questions though.
1. Does this mean that all the headers reside in skb->data - skb->head or
just the ethernet header ?
2. Or is it that the TCP and IP headers are considered part of data in
sk_buff and are stored in the skb->tail - skb->data section ?
I ask the second questions because I saw
skb->h.raw = skb->nh.raw = skb->data;
in netif_receive_skb() (/net/core/dev.c) function. With this statement it
would mean that there is no line of seperation between the two layers. Or
am I missing something here ?
Thanks,
Rahul.
On Tue, 22 Jun 2004, Jonathan Corbet wrote:
> > In this structure there are pointers called headroom, data, tailroom and
> > end. Does anyone know what these are used for. Or can anyone point me to a
> > good explanation for these fields.
>
> There is a basic discussion in chapter 14 of Linux Device Drivers which
> you can read online at http://www.xml.com/ldd/chapter/book/index.html.
>
> jon
>
> Jonathan Corbet
> Executive editor, LWN.net
> corbet@lwn.net
>
next prev parent reply other threads:[~2004-06-22 23:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 20:48 rahul b jain cs student
2004-06-22 21:24 ` Jonathan Corbet
2004-06-22 23:03 ` rahul b jain cs student [this message]
2004-06-23 18:45 ` Question about ip_rcv() function rahul b jain cs student
2004-06-23 18:50 ` David S. Miller
2004-06-23 20:22 ` rahul b jain cs student
2004-06-23 20:32 ` David S. Miller
2004-06-23 20:43 ` rahul b jain cs student
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=Pine.GSO.4.58.0406221855490.15759@chrome.njit.edu \
--to=rbj2@oak.njit.edu \
--cc=corbet@lwn.net \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®