From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net: increase receive packet quantum
Date: Tue, 04 Nov 2008 14:48:00 -0800 (PST) [thread overview]
Message-ID: <20081104.144800.158229098.davem@davemloft.net> (raw)
In-Reply-To: <20081103212521.15e12168@extreme>
From: Stephen Hemminger <shemminger@vyatta.com>
Date: Mon, 3 Nov 2008 21:25:21 -0800
> On Mon, 03 Nov 2008 17:24:28 -0800 (PST)
> David Miller <davem@davemloft.net> wrote:
>
> > I'll apply this to net-next-2.6, thanks Stephen.
>
> Maybe you want it as part of the tbench regression recovery in 2.6.28?
> it seems mostly harmless.
Maybe...
I'd rather have it cook in net-next-2.6 for a while.
Taking up more than a jiffie in softirq context is
bordering on anti-social and could cause problems
especially for RT'ish stuff.
And I'm pretty sure that's why I made the change.
prev parent reply other threads:[~2008-11-04 22:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 21:03 [PATCH] net: increase receive packet quantum Stephen Hemminger
2008-11-04 1:24 ` David Miller
2008-11-04 5:25 ` Stephen Hemminger
2008-11-04 22:48 ` David Miller [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=20081104.144800.158229098.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox