From: Roland Dreier <rdreier@cisco.com>
To: David Miller <davem@davemloft.net>
Cc: andi@firstfloor.org, Santwona.Behera@Sun.COM,
netdev@vger.kernel.org, jeff@garzik.org, Matheos.Worku@Sun.COM,
Michael.Speer@Sun.COM, gkernel-commit@lists.sourceforge.net
Subject: Re: [PATCH 0/3] Add support for rx flow hash configuration in a network device
Date: Mon, 30 Jun 2008 20:33:45 -0700 [thread overview]
Message-ID: <adaabh2ffc6.fsf@cisco.com> (raw)
In-Reply-To: <20080629.134936.139001500.davem@davemloft.net> (David Miller's message of "Sun, 29 Jun 2008 13:49:36 -0700 (PDT)")
> We've discussed this before and Jeff Garzik and I already told
> everyone that we want to make this configurable and ethtool is
> the way to do it no matter how adhoc and device specific the
> interfaces might end up being.
I think it was a few weeks ago that Jeff said:
I know user interfaces are annoying because you have to think about
chips other than your own, but that's life. Other hardware vendors have
to do it too.
Letting each driver have a different user interface is /unfriendly/ to
both developers users.
I guess as long as you stick an "ethtool" in front of the different
interfaces it all becomes OK.
- R.
next prev parent reply other threads:[~2008-07-01 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-28 0:06 [PATCH 0/3] Add support for rx flow hash configuration in a network device Santwona Behera
2008-06-29 12:17 ` Andi Kleen
2008-06-29 20:49 ` David Miller
2008-06-30 0:15 ` Andi Kleen
2008-07-01 3:33 ` Roland Dreier [this message]
2008-07-01 4:42 ` David Miller
2008-07-02 10:50 ` 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=adaabh2ffc6.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=Matheos.Worku@Sun.COM \
--cc=Michael.Speer@Sun.COM \
--cc=Santwona.Behera@Sun.COM \
--cc=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=gkernel-commit@lists.sourceforge.net \
--cc=jeff@garzik.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).