From: "Chris Friesen" <cfriesen@nortel.com>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: question on sky2 driver panic
Date: Mon, 15 Oct 2007 23:16:16 -0600 [thread overview]
Message-ID: <47144920.4010402@nortel.com> (raw)
In-Reply-To: <20071015150408.22f31d77@freepuppy.rosehill>
Stephen Hemminger wrote:
> Maybe TIPC can't handle fragmented receive buffers. The sky2 driver
> generates skb's with header and multiple pages if MTU is big enough.
> For 9K MTU that would be 1K of data + 2 4K pages. The protocols are
> supposed to be smart enough to handle this, but TIPC is rarely used.
We already had to modify tipc to handle fragmented receive buffers when
we had memory allocation errors on the e1000 and moved to fragmented
skbs in that driver.
Our version of the e1000 passes 200 bytes in the initial chunk, and the
rest in fragments. tipc currently handles that without any difficulty.
I was just checking more to see if there were any known issues in this
area that have been fixed in more recent driver versions.
Chris
next prev parent reply other threads:[~2007-10-16 5:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 20:17 question on sky2 driver panic Chris Friesen
2007-10-15 22:04 ` Stephen Hemminger
2007-10-16 5:16 ` Chris Friesen [this message]
2007-10-16 5:20 ` David Miller
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=47144920.4010402@nortel.com \
--to=cfriesen@nortel.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).