From: John Heffner <jheffner@psc.edu>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux@syskonnect.de, netdev@vger.kernel.org
Subject: Re: sk98lin, jumbo frames, and memory fragmentation
Date: Mon, 01 Oct 2007 16:44:50 -0400 [thread overview]
Message-ID: <47015C42.9070809@psc.edu> (raw)
In-Reply-To: <47015A24.7000701@nortel.com>
Yes it has this problem. I've observed it in practice on a busy firewall.
-John
Chris Friesen 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.
>
>
> Thanks,
>
> Chris
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-10-01 20:44 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 [this message]
2007-10-01 20:47 ` Jeff Garzik
2007-10-01 21:08 ` Chris Friesen
2007-10-01 21:06 ` Stephen Hemminger
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=47015C42.9070809@psc.edu \
--to=jheffner@psc.edu \
--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).