From: Phil Sutter <phil@nwl.cc>
To: netdev@vger.kernel.org
Subject: Re: linear sk_buff
Date: Wed, 5 May 2010 21:32:36 +0200 [thread overview]
Message-ID: <20100505193204.D847B4CD45@orbit.nwl.cc> (raw)
In-Reply-To: <o2kdac45061005051212na062f611m1c87240c367b5d38@mail.gmail.com>
Hi,
On Wed, May 05, 2010 at 10:12:06PM +0300, Mark Ryden wrote:
> I would appreciate if someone in this mailing list can say in a
> sentence or two what is a linear
> sk_buff and what is a non linear sk_buff; does it has to do with fragmentation?
> (I am sure that many know the answer, but I am confused and googling
> made me overconfused)
As far as I can tell, linear and non-linear sk_buffs differ in how the
data they contain is kept internally. Linear sk_buffs are trivial, it's
data resides in one, continuous block. In non-linear sk_buffs, data is
spread across multiple junks, organised in a data structure comparable
to e.g. scatterlists.
For further information, I'd highly recommend David Miller's "how SKBs
work": http://vger.kernel.org/~davem/skb.html .
Greetings, Phil
next prev parent reply other threads:[~2010-05-05 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 19:12 linear sk_buff Mark Ryden
2010-05-05 19:32 ` Phil Sutter [this message]
2010-05-05 19:35 ` Rémi Denis-Courmont
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=20100505193204.D847B4CD45@orbit.nwl.cc \
--to=phil@nwl.cc \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).