From: Ben Hutchings <ben@decadent.org.uk>
To: Venkat Duvvuru <VenkatKumar.Duvvuru@Emulex.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v7 ethtool 2/2] ethtool: Support for configurable RSS hash key
Date: Sun, 21 Sep 2014 23:38:10 +0100 [thread overview]
Message-ID: <1411339090.20019.28.camel@decadent.org.uk> (raw)
In-Reply-To: <1411337728.20019.26.camel@decadent.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1586 bytes --]
On Sun, 2014-09-21 at 23:15 +0100, Ben Hutchings wrote:
> On Sun, 2014-09-21 at 21:52 +0100, Ben Hutchings wrote:
> > On Tue, 2014-07-22 at 17:51 +0530, Venkat Duvvuru wrote:
> > > This ethtool patch will primarily implement the parser for the options provided
> > > by the user for get and set rxfh before invoking the ioctl.
> > > This patch also has
> > > 1. Ethtool man page changes which describes the Usage of
> > > get and set rxfh options.
> > > 2. Test cases for get and set rxfh in test-cmdline.c
> > >
> > > Signed-off-by: Venkat Duvvuru <VenkatKumar.Duvvuru@Emulex.com>
> > [...]
> >
> > FAIL: test-cmdline
> > ==================
> >
> > E: ethtool --rxfh devname hkey foo returns 0
> > E: ethtool -X devname hkey foo returns 0
> >
> > The problem with these test cases is we can't parse the hash key (and
> > reject "foo") until after we start sending ioctls. test-cmdline doesn't
> > include any mocking of ioctls, but instead makes each test successful if
> > it calls an ioctl.
>
> It also doesn't work for me with an older kernel version (I tested on
> Linux 3.14). I don't know why that is, as your fallback code does look
> reasonable.
Oops, I tested the previous version of this on 3.14. The latest version
does work correctly.
I'll apply your changes and then disable the two failing test cases for
now. Thanks for persisting with this.
Ben.
--
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
prev parent reply other threads:[~2014-09-21 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1406031667-30364-1-git-send-email-VenkatKumar.Duvvuru@Emulex.com>
2014-07-22 12:21 ` [PATCH v7 ethtool 1/2] ethtool: Support for configurable RSS hash key Venkat Duvvuru
2014-07-22 12:21 ` [PATCH v7 ethtool 2/2] " Venkat Duvvuru
2014-09-21 20:52 ` Ben Hutchings
2014-09-21 22:15 ` Ben Hutchings
2014-09-21 22:38 ` Ben Hutchings [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=1411339090.20019.28.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=VenkatKumar.Duvvuru@Emulex.com \
--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