From: David Miller <davem@davemloft.net>
To: frank.blaschka@de.ibm.com
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 05:11:33 -0800 (PST) [thread overview]
Message-ID: <20100121.051133.102632014.davem@davemloft.net> (raw)
In-Reply-To: <20100121123722.GA13815@tuxmaker.boeblingen.de.ibm.com>
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... :-)
next prev parent reply other threads:[~2010-01-21 13:11 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 [this message]
2010-01-21 13:48 ` Blaschka
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=20100121.051133.102632014.davem@davemloft.net \
--to=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).