From: Jeff Garzik <jeff@garzik.org>
To: akpm@linux-foundation.org
Cc: netdev@vger.kernel.org, mingo@elte.hu, aabdulla@nvidia.com
Subject: Re: [patch 03/13] forcedeth: improve NAPI logic
Date: Fri, 11 May 2007 03:11:04 -0400 [thread overview]
Message-ID: <46441708.7020605@garzik.org> (raw)
In-Reply-To: <200705110552.l4B5qlHx007795@shell0.pdx.osdl.net>
akpm@linux-foundation.org wrote:
> From: Ingo Molnar <mingo@elte.hu>
>
> Another forcedeth.c thing: i noticed that its NAPI handler does not do
> tx-ring processing. The patch below implements this - tested on DESC_VER_2
> hardware, with CONFIG_FORCEDETH_NAPI=y.
>
>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> Cc: Ayaz Abdulla <aabdulla@nvidia.com>
> ---
> Auke said:
>
> the patch needs to be improved.
>
> The following needs to be done when NAPI is enabled:
> - remove the tx handling within the ISRs
> - mask off the tx interrupts within the ISRs that handle tx processing
> - re-enable tx interrupts within the NAPI handler
> - add tx handling within the NAPI handler (this patch covers it)
>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> ---
>
> drivers/net/forcedeth.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
This was NAK'd at least twice?
It's a half-finished project. You need to do more, if moving TX from
irq handler to NAPI.
I'm definitely not applying it, and as its incomplete, it definitely
isn't suitable for upstream.
Jeff
prev parent reply other threads:[~2007-05-11 7:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 5:52 [patch 03/13] forcedeth: improve NAPI logic akpm
2007-05-11 7:11 ` Jeff Garzik [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=46441708.7020605@garzik.org \
--to=jeff@garzik.org \
--cc=aabdulla@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=mingo@elte.hu \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).