From: Jeff Garzik <jeff@garzik•org>
To: Francois Romieu <romieu@fr•zoreil.com>
Cc: David Miller <davem@davemloft•net>,
netdev@vger•kernel.org, shemminger@linux-foundation•org,
rusty@rustcorp•com.au
Subject: Re: [PATCH RFX]: napi_struct V3
Date: Tue, 24 Jul 2007 03:33:41 -0400 [thread overview]
Message-ID: <46A5AB55.90007@garzik.org> (raw)
In-Reply-To: <20070724071201.GA7134@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> David Miller <davem@davemloft•net> :
> [...]
>> I also didn't play with turning off NAPI in kconfig where drivers
>> allow that, can we just get rid of that crap already? :-/
>
> Would it be accepted for 2.6.23 or must it be considered post-2.6.23 ?
The merge window is closed, so not 2.6.23.
The cases where Kconfig allows selection of NAPI-or-not is generally
either (a) the author considers one path new and relatively unproven or
(b) the author has not bothered to figure out which is the best choice,
and instead just offers both rather than doing the legwork to find out.
Either way, individual cases must be examined and it is not necessarily
just a cleanup.
Jeff
next prev parent reply other threads:[~2007-07-24 7:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 4:07 [PATCH RFX]: napi_struct V3 David Miller
2007-07-24 4:47 ` Rusty Russell
2007-07-24 5:47 ` David Miller
2007-07-24 6:21 ` Rusty Russell
2007-07-25 0:45 ` David Miller
2007-07-25 1:15 ` Rusty Russell
2007-07-25 1:47 ` David Miller
2007-07-25 2:33 ` Rusty Russell
2007-07-25 4:29 ` David Miller
2007-07-25 5:09 ` Rusty Russell
2007-07-25 5:12 ` David Miller
2007-07-25 5:10 ` David Miller
2007-07-24 7:12 ` Francois Romieu
2007-07-24 7:33 ` Jeff Garzik [this message]
2007-07-24 7:35 ` David Miller
2007-07-28 15:21 ` Roland Dreier
2007-07-29 5:30 ` 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=46A5AB55.90007@garzik.org \
--to=jeff@garzik$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=romieu@fr$(echo .)zoreil.com \
--cc=rusty@rustcorp$(echo .)com.au \
--cc=shemminger@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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