From: Ganesh Venkatesan <ganesh.venkatesan@gmail.com>
To: Dan Aloni <da-x@monatomic.org>
Cc: Francois Romieu <romieu@fr.zoreil.com>,
Linux Kernel List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: workaround large MTU and N-order allocation failures
Date: Mon, 19 Sep 2005 10:25:29 -0700 [thread overview]
Message-ID: <5fc59ff305091910252447d363@mail.gmail.com> (raw)
In-Reply-To: <20050919071358.GA7107@localdomain>
82546GB supports an incoming Rx packet to be received in multiple rx
buffers. A driver that enables this feature is under test currently.
What version of the e1000 are you using?
ganesh.
On 9/19/05, Dan Aloni <da-x@monatomic.org> wrote:
> On Mon, Sep 19, 2005 at 01:08:22AM +0200, Francois Romieu wrote:
> > Dan Aloni <da-x@monatomic.org> :
> > [...]
> > > The problem with large MTU is external memory fragmentation in
> > > the buddy system following high workload, causing alloc_skb() to
> > > fail.
> >
> > If the issue hits the Rx path, it is probably the responsibility of
> > the device driver. Which kind of hardware do you use ?
>
> We are using a SuperMicro board and the network driver is e1000. The
> revision of the chipset is 82546GB-copper (maps to e1000_82546_rev_3).
>
> This particular chipset does not support packet splitting, so we
> are looking for a hack on the skb layer.
>
> --
> Dan Aloni
> da-x@monatomic.org, da-x@colinux.org, da-x@gmx.net
> -
> 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:[~2005-09-19 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-18 14:35 workaround large MTU and N-order allocation failures Dan Aloni
2005-09-18 23:08 ` Francois Romieu
2005-09-19 7:13 ` Dan Aloni
2005-09-19 17:25 ` Ganesh Venkatesan [this message]
2005-09-20 14:25 ` Dan Aloni
2005-09-19 6:31 ` Nick Piggin
2005-09-19 13:38 ` Al Boldi
2005-09-20 14:34 ` Dan Aloni
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=5fc59ff305091910252447d363@mail.gmail.com \
--to=ganesh.venkatesan@gmail.com \
--cc=da-x@monatomic.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=romieu@fr.zoreil.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.