From: "Chris Friesen" <cfriesen@nortel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@vger.kernel.org
Subject: Re: jumbo frames and memory fragmentation
Date: Mon, 17 Jul 2006 11:16:19 -0600 [thread overview]
Message-ID: <44BBC5E3.60008@nortel.com> (raw)
In-Reply-To: <E1G104c-0007qF-00@gondolin.me.apana.org.au>
Herbert Xu wrote:
> Chris Friesen <cfriesen@nortel.com> wrote:
>>Looking at the page-splitting code, it says "82571 and greater support
>>packet-split...". We're running the 82546GB device. Looks like it
>>won't help me.
>
>
> Well, time to fork out for a new card then :)
I wish. This is an embedded ATCA board. I'm not going to get a respin
just because it doesn't deal well with jumbo frames.
Chris
prev parent reply other threads:[~2006-07-17 17:16 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
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 [this message]
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=44BBC5E3.60008@nortel.com \
--to=cfriesen@nortel.com \
--cc=herbert@gondor.apana.org.au \
--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).