From: Jan Glauber <jang@linux.vnet.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: frank.blaschka@de.ibm.com, netdev@vger.kernel.org,
linux-s390@vger.kernel.org
Subject: Re: [RFC] qeth: exploit gro for layer 3 driver
Date: Thu, 21 Jan 2010 15:35:27 +0100 [thread overview]
Message-ID: <1264084527.5880.45.camel@bender> (raw)
In-Reply-To: <20100121.060354.119388130.davem@davemloft.net>
On Thu, 2010-01-21 at 06:03 -0800, David Miller wrote:
> From: Blaschka <frank.blaschka@de.ibm.com>
> Date: Thu, 21 Jan 2010 14:48:45 +0100
>
> > So the qeth driver can not disable qdio IRQs (I guess this is a
> > major reason why not using NAPI) and poll the data.
>
> Just because you cannot stop the events from coming in
> doesn't mean you can't just queue them up in software
> or similar.
The data is already queued (since qdio stands for queued direct I/O).
Currently qdio gets the interrupt, does some processing and
tells qeth which buffers contain the new data.
So the only question is what needs to be different for NAPI
regarding the event signaling.
--Jan
> The important bits you get are:
>
> 1) RX ring depletion and packet processing all from software
> interrupt context
>
> 2) transparent GRO support, without the generic code having
> to disclose most of the GRO internals to drivers
>
> I think it can be done.
>
> I have a similar issue as your's with the Sun virtualized network
> driver (I can't really stop the hypervisor events from pouring in) on
> sparc64 and I plan to add NAPI support to it.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-s390" 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:[~2010-01-21 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 12:37 [RFC] qeth: exploit gro for layer 3 driver Blaschka
2010-01-21 13:11 ` David Miller
2010-01-21 13:48 ` Blaschka
2010-01-21 14:03 ` David Miller
2010-01-21 14:35 ` Jan Glauber [this message]
2010-01-22 6:14 ` Blaschka
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=1264084527.5880.45.camel@bender \
--to=jang@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=frank.blaschka@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--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).