From: Stephen Hemminger <shemminger@linux-foundation.org>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: linux@syskonnect.de, netdev@vger.kernel.org
Subject: Re: sk98lin, jumbo frames, and memory fragmentation
Date: Mon, 1 Oct 2007 14:06:27 -0700 [thread overview]
Message-ID: <20071001140627.1e2e665f@freepuppy.rosehill> (raw)
In-Reply-To: <47015A24.7000701@nortel.com>
On Mon, 01 Oct 2007 14:35:48 -0600
"Chris Friesen" <cfriesen@nortel.com> wrote:
>
> Hi all,
>
> We're considering some hardware that uses the sk98lin network hardware,
> and we'll be using jumbo frames. Looking at the driver, when using a
> 9KB MTU it seems like it would end up trying to atomically allocate a
> 16KB buffer.
>
> Has anyone heard of this been a problem? It would seem like trying to
> atomically allocate four physically contiguous pages could become tricky
> after the system has been running for a while.
>
> The reason I ask is that we ran into this with the e1000. Before they
> added the new jumbo frame code it was trying to atomically allocate 32KB
> buffers and we would start getting allocation failures after a month or
> so of uptime.
>
> Any information anyone can provide would be appreciated.
Adding fragmentation support to skge driver is on my list of
possible extensions. sky2 driver already supports it (yet one
more feature that the vendor sk98lin driver doesn't do).
--
Stephen Hemminger <shemminger@linux-foundation.org>
next prev parent reply other threads:[~2007-10-01 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 20:35 sk98lin, jumbo frames, and memory fragmentation Chris Friesen
2007-10-01 20:44 ` John Heffner
2007-10-01 20:47 ` Jeff Garzik
2007-10-01 21:08 ` Chris Friesen
2007-10-01 21:06 ` Stephen Hemminger [this message]
2007-10-01 21:15 ` Chris Friesen
2007-10-01 21:57 ` Stephen Hemminger
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=20071001140627.1e2e665f@freepuppy.rosehill \
--to=shemminger@linux-foundation.org \
--cc=cfriesen@nortel.com \
--cc=linux@syskonnect.de \
--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).