From: Ben Hutchings <bhutchings@solarflare.com>
To: <netdev@vger.kernel.org>
Cc: <linux-net-drivers@solarflare.com>
Subject: [PATCH ethtool 4/4] ethtool.8: Improve description of RX NFC options
Date: Fri, 17 Feb 2012 20:55:32 +0000 [thread overview]
Message-ID: <1329512132.2822.8.camel@bwh-desktop> (raw)
In-Reply-To: <1329512042.2822.4.camel@bwh-desktop>
State explicitly that arguments beginning with 'flow-type' will
insert or update a rule.
Refer consistently to 'flow type' rather than 'network traffic type'.
Refer to 'options and rules', covering both flow hashing and
steering/filtering.
Signed-off-by: Ben Hutchings <bhutchings@solarflare.com>
---
ethtool.8.in | 9 +++++----
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/ethtool.8.in b/ethtool.8.in
index 4c46096..3567352 100644
--- a/ethtool.8.in
+++ b/ethtool.8.in
@@ -590,10 +590,10 @@ The precise meanings of these type flags differ between drivers.
.RE
.TP
.B \-n \-u \-\-show\-nfc \-\-show\-ntuple
-Retrieves the receive network flow classification configurations.
+Retrieves receive network flow classification options or rules.
.TP
.BR rx\-flow\-hash \ \*(FL
-Retrieves the hash options for the specified network traffic type.
+Retrieves the hash options for the specified flow type.
.TS
nokeep;
lB l.
@@ -615,10 +615,10 @@ Retrieves the RX classification rule with the given ID.
.RE
.TP
.B \-N \-U \-\-config\-nfc \-\-config\-ntuple
-Configures the receive network flow classification.
+Configures receive network flow classification options or rules.
.TP
.BR rx\-flow\-hash \ \*(FL \: \*(HO
-Configures the hash options for the specified network traffic type.
+Configures the hash options for the specified flow type.
.TS
nokeep;
lB l.
@@ -636,6 +636,7 @@ T}
.TE
.TP
.B flow\-type \*(NC
+Inserts or updates a classification rule for the specified flow type.
.TS
nokeep;
lB l.
--
1.7.7.6
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
prev parent reply other threads:[~2012-02-17 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 20:54 [PATCH ethtool 0/4] RX NFC cleanup Ben Hutchings
2012-02-17 20:54 ` [PATCH ethtool 1/4] Move '--flash' down the list of options Ben Hutchings
2012-02-17 20:55 ` [PATCH ethtool 2/4] Merge RX NFC options Ben Hutchings
2012-02-17 20:55 ` [PATCH ethtool 3/4] ethtool.8: Don't mention the 'clear rule' action for NFC rules Ben Hutchings
2012-02-17 20:55 ` 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=1329512132.2822.8.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.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;
as well as URLs for NNTP newsgroup(s).