From: Blaschka <frank.blaschka@de.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [RFC] qeth: exploit gro for layer 3 driver
Date: Thu, 21 Jan 2010 14:48:45 +0100 [thread overview]
Message-ID: <20100121134845.GA28645@tuxmaker.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20100121.051133.102632014.davem@davemloft.net>
On Thu, Jan 21, 2010 at 05:11:33AM -0800, David Miller wrote:
> From: Blaschka <frank.blaschka@de.ibm.com>
> Date: Thu, 21 Jan 2010 13:37:22 +0100
>
> > Since the qeth driver can not use NAPI I would like to hear
> > your opinion about following approach to exploit GRO.
>
> Can you remind us why it can't use NAPI?
>
> I personally find it hard to believe... :-)
Sure, let me try ...
on s/390 we neither have have a PCI bus nor a DMA transfer. We have
a common software component called qdio which does a DMA like data
transfer to/from the hardware. The inbound interface between qeth
and qdio is a tasklet running under the control of qdio. So the qeth
driver can not disable qdio IRQs (I guess this is a major reason why
not using NAPI) and poll the data.
qdio is also used for other s/390 non network drivers (e.g. fcp) so
changing this component is rather difficult and out of qeth scope.
The qdio framework already provides a bottomhalf so todays approach
to call netif_rx seems to be questionable anyway ...
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" 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 13:48 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 [this message]
2010-01-21 14:03 ` David Miller
2010-01-21 14:35 ` Jan Glauber
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=20100121134845.GA28645@tuxmaker.boeblingen.de.ibm.com \
--to=frank.blaschka@de.ibm.com \
--cc=davem@davemloft.net \
--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