From: Ben Hutchings <ben@decadent.org.uk>
To: Edward Cree <ecree@solarflare.com>, Ben Hutchings <bwh@kernel.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH ethtool 3/3] Documentation for IPv6 NFC
Date: Sun, 13 Mar 2016 16:47:18 +0000 [thread overview]
Message-ID: <1457887638.3331.33.camel@decadent.org.uk> (raw)
In-Reply-To: <56C1E7FA.6050601@solarflare.com>
[-- Attachment #1: Type: text/plain, Size: 3534 bytes --]
On Mon, 2016-02-15 at 15:00 +0000, Edward Cree wrote:
> Leaves 'src-ip' and 'dst-ip' documented as taking x.x.x.x, because there's
> more low-level nroff here than I can parse, let alone emit.
>
> Signed-off-by: Edward Cree <ecree@solarflare.com>
> ---
> ethtool.8.in | 34 +++++++++++++++++++++++++---------
> ethtool.c | 4 +++-
> 2 files changed, 28 insertions(+), 10 deletions(-)
>
> diff --git a/ethtool.8.in b/ethtool.8.in
> index eeffa70..5c0a9e3 100644
> --- a/ethtool.8.in
> +++ b/ethtool.8.in
> @@ -74,7 +74,7 @@
> .\"
> .\" \(*NC - Network Classifier type values
> .\"
> -.ds NC \fBether\fP|\fBip4\fP|\fBtcp4\fP|\fBudp4\fP|\fBsctp4\fP|\fBah4\fP|\fBesp4\fP
> +.ds NC \fBether\fP|\fBip4\fP|\fBip6\fP|\fBtcp4\fP|\fBudp4\fP|\fBsctp4\fP|\fBah4\fP|\fBesp4\fP|\fBtcp6\fP|\fBudp6\fP|\fBah6\fP|\fBesp6\fP|\fBsctp6\fP
Why is ip6 added in the middle of the IPv4 flow-types here...
[...]
> @@ -676,11 +678,17 @@ nokeep;
> lB l.
> ether Ethernet
> ip4 Raw IPv4
> +ip6 Raw IPv6
> tcp4 TCP over IPv4
> udp4 UDP over IPv4
> sctp4 SCTP over IPv4
> ah4 IPSEC AH over IPv4
> esp4 IPSEC ESP over IPv4
> +tcp6 TCP over IPv6
> +udp6 UDP over IPv6
> +sctp6 SCTP over IPv6
> +ah6 IPSEC AH over IPv6
> +esp6 IPSEC ESP over IPv6
...and here...
[...]
> --- a/ethtool.c
> +++ b/ethtool.c
> @@ -4108,13 +4108,15 @@ static const struct option {
> "Configure Rx network flow classification options or rules",
> " rx-flow-hash tcp4|udp4|ah4|esp4|sctp4|"
> "tcp6|udp6|ah6|esp6|sctp6 m|v|t|s|d|f|n|r... |\n"
> - " flow-type ether|ip4|tcp4|udp4|sctp4|ah4|esp4\n"
> + " flow-type ether|ip4|tcp4|udp4|sctp4|ah4|esp4|"
> + "ip6|tcp6|udp6|ah6|esp6|sctp6\n"
...but not here?
> " [ src %x:%x:%x:%x:%x:%x [m %x:%x:%x:%x:%x:%x] ]\n"
> " [ dst %x:%x:%x:%x:%x:%x [m %x:%x:%x:%x:%x:%x] ]\n"
> " [ proto %d [m %x] ]\n"
> " [ src-ip %d.%d.%d.%d [m %d.%d.%d.%d] ]\n"
> " [ dst-ip %d.%d.%d.%d [m %d.%d.%d.%d] ]\n"
> " [ tos %d [m %x] ]\n"
> + " [ tclass %d [m %x] ]\n"
Missing nexthdr?
Ben.
> " [ l4proto %d [m %x] ]\n"
> " [ src-port %d [m %x] ]\n"
> " [ dst-port %d [m %x] ]\n"
> The information contained in this message is confidential and is
> intended for the addressee(s) only. If you have received this message
> in error, please notify the sender immediately and delete the
> message. Unless you are an addressee (or authorized to receive for an
> addressee), you may not use, copy or disclose to anyone this message
> or any information contained in this message. The unauthorized use,
> disclosure, copying or alteration of this message is strictly
> prohibited.
--
Ben Hutchings
If at first you don't succeed, you're doing about average.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-03-13 16:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 14:56 [PATCH ethtool 0/3] IPv6 RXNFC Edward Cree
2016-02-15 14:59 ` [PATCH ethtool 1/3] ethtool-copy.h: sync with net-next Edward Cree
2016-02-15 14:59 ` [PATCH ethtool 2/3] Add IPv6 support to NFC Edward Cree
2016-03-13 16:43 ` Ben Hutchings
2016-03-16 14:53 ` Edward Cree
2016-03-16 17:15 ` Ben Hutchings
2016-02-15 15:00 ` [PATCH ethtool 3/3] Documentation for IPv6 NFC Edward Cree
2016-03-13 16:47 ` Ben Hutchings [this message]
2016-03-16 14:54 ` Edward Cree
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=1457887638.3331.33.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=bwh@kernel.org \
--cc=ecree@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