From: Stephen Hemminger <shemminger@vyatta.com>
To: Vladislav Bolkhovitin <vst@vlnb.net>
Cc: "James Bottomley" <James.Bottomley@suse.de>,
"Lukas Kolbe" <lkolbe@techfak.uni-bielefeld.de>,
"Kai Mäkisara" <kai.makisara@kolumbus.fi>,
"FUJITA Tomonori" <fujita.tomonori@lab.ntt.co.jp>,
linux-scsi@vger.kernel.org,
"Kashyap Desai" <Kashyap.Desai@lsi.com>,
netdev@vger.kernel.org
Subject: Re: After memory pressure: can't read from tape anymore
Date: Tue, 14 Dec 2010 14:23:20 -0800 [thread overview]
Message-ID: <20101214142320.27d911d5@nehalam> (raw)
In-Reply-To: <4D07D519.70800@vlnb.net>
On Tue, 14 Dec 2010 23:35:37 +0300
Vladislav Bolkhovitin <vst@vlnb.net> wrote:
> What is interesting to me in this regard is how networking with 9K jumbo
> frames manages to work acceptably reliable? Jumbo frames used
> sufficiently often, including under high memory pressure.
>
> I'm not a deep networking guru, but network drivers need to allocate
> physically continual memory for skbs, which means 16K per 9K packet,
> which means order 2 allocations per skb.
Good network drivers support fragmentation and allocate a small portion
for the header and allocate pages for the rest. This requires no higher
order allocation. The networking stack takes fragmented data coming
in and does the necessary copy/merging to access contiguous headers.
There are still some crap network drivers that require large contiguous
allocation. These should not be used with jumbo frames in real
environments.
--
next prev parent reply other threads:[~2010-12-14 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1290971729.2814.13.camel@larosa>
[not found] ` <alpine.LNX.2.00.1011291857420.7923@kai.makisara.local>
[not found] ` <20101203212453W.fujita.tomonori@lab.ntt.co.jp>
[not found] ` <4CF905D1.6050903@kolumbus.fi>
[not found] ` <1291388776.2881.4.camel@mulgrave.site>
[not found] ` <1291395815.2814.376.camel@larosa>
[not found] ` <1291399814.2881.66.camel@mulgrave.site>
2010-12-14 20:35 ` After memory pressure: can't read from tape anymore Vladislav Bolkhovitin
2010-12-14 22:23 ` Stephen Hemminger [this message]
2010-12-15 16:27 ` Vladislav Bolkhovitin
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=20101214142320.27d911d5@nehalam \
--to=shemminger@vyatta.com \
--cc=James.Bottomley@suse.de \
--cc=Kashyap.Desai@lsi.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=kai.makisara@kolumbus.fi \
--cc=linux-scsi@vger.kernel.org \
--cc=lkolbe@techfak.uni-bielefeld.de \
--cc=netdev@vger.kernel.org \
--cc=vst@vlnb.net \
/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).