mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shane Hathaway <shane@hathawaymix.org>
To: Chris Leech <chris.leech@gmail.com>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] e1000 rx buffer allocation
Date: Fri, 27 Aug 2004 20:27:48 -0600	[thread overview]
Message-ID: <200408272027.49059.shane@hathawaymix.org> (raw)
In-Reply-To: <41b516cb04082711363a009dbc@mail.gmail.com>

On Friday 27 August 2004 12:36 pm, Chris Leech wrote:
> As for moving the allocations out of the hard interrupt context, e1000
> was one of several drivers that tried that a few years back by using
> tasklets.  What I found is that if you split the allocation from the
> receive processing, it's far to easy to generate an interrupt load
> which starves the skb allocations.  The result is that you
> continuously use all of the buffers then stall while they all get
> replaced, and performance is horrible.  But if the patch works for
> your network load ...

We're getting 6000 interrupts per second, but the box handles it with ease.  
We're getting zero loss now, but I guess with slower hardware or fewer 
buffers, scheduling would be a problem.

> A better approach for improving jumbo frame allocations might be to
> use multiple smaller buffers for each receive, something the PRO/1000
> hardware can do but the e1000 driver has never taken advantage of.

Yes, that would be a far better solution.  I had no idea the card could do 
that.  Are there specs on this hardware somewhere?  Although my patch works, 
I don't want to stick with a temporary solution.

Shane

      parent reply	other threads:[~2004-08-28  2:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 23:35 shane
2004-08-27  1:18 ` David S. Miller
2004-08-27  1:18 ` David S. Miller
2004-08-27 18:36   ` Chris Leech
2004-08-27 19:36     ` David S. Miller
2004-08-28  2:27     ` Shane Hathaway [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=200408272027.49059.shane@hathawaymix.org \
    --to=shane@hathawaymix.org \
    --cc=chris.leech@gmail.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®