From: "Chris Friesen" <cfriesen@nortel.com>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, netdev@vger.kernel.org
Subject: Re: jumbo frames and memory fragmentation
Date: Fri, 30 Jun 2006 17:35:34 -0600 [thread overview]
Message-ID: <44A5B546.3010606@nortel.com> (raw)
In-Reply-To: <20060630184820.GA9558@2ka.mipt.ru>
Evgeniy Polyakov wrote:
> It definitely will.
> Packet split in hardware means separating data and headers into
> different pages in different reads, while software page split means that
> skb has a list of fragments where part of the packet will be DMAed, so
> jumbo frame will be converted into several pages.
Maybe I'm looking at the wrong code then. Can you point me to where
this "software page split" is handled?
Chris
next prev parent reply other threads:[~2006-06-30 23:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 18:54 jumbo frames and memory fragmentation Chris Friesen
2006-06-30 13:01 ` Herbert Xu
2006-06-30 17:53 ` Chris Friesen
2006-06-30 18:48 ` Evgeniy Polyakov
2006-06-30 23:35 ` Chris Friesen [this message]
2006-07-01 0:04 ` Jesse Brandeburg
2006-07-08 22:25 ` Evgeniy Polyakov
2006-07-13 12:13 ` Herbert Xu
2006-07-17 17:16 ` Chris Friesen
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=44A5B546.3010606@nortel.com \
--to=cfriesen@nortel.com \
--cc=herbert@gondor.apana.org.au \
--cc=johnpol@2ka.mipt.ru \
--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).