From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: ecree.xilinx@gmail.com, jdamato@fastly.com, davem@davemloft.net,
mkubecek@suse.cz, martin.lau@linux.dev, netdev@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH ethtool-next v2] rxclass: Make output for RSS context action explicit
Date: Tue, 12 Nov 2024 07:40:47 -0800 [thread overview]
Message-ID: <20241112074047.44490c6e@kernel.org> (raw)
In-Reply-To: <978e1192c07e970b8944c2a729ae42bf97667a53.1731107871.git.dxu@dxuuu.xyz>
On Mon, 11 Nov 2024 12:05:38 -0700 Daniel Xu wrote:
> - if (fsp->flow_type & FLOW_RSS)
> - fprintf(stdout, "\tRSS Context ID: %u\n", rss_context);
> -
> if (fsp->ring_cookie == RX_CLS_FLOW_DISC) {
> fprintf(stdout, "\tAction: Drop\n");
> } else if (fsp->ring_cookie == RX_CLS_FLOW_WAKE) {
> fprintf(stdout, "\tAction: Wake-on-LAN\n");
> + } else if (fsp->flow_type & FLOW_RSS) {
> + u64 queue = ethtool_get_flow_spec_ring(fsp->ring_cookie);
> +
> + fprintf(stdout, "\tAction: Direct to RSS context id %u", rss_context);
Do you have strong feelings about the change in formatting?
Looking at Ed's comment on the new test made me wonder if the change
in capitalization is for the better.
Action: Direct to RSS context id 1 (queue base offset: 2)
vs
Action: Direct to RSS Context ID: 1 (queue base offset: 2)
Given "id" is a word (: I like the ID format, the extra colon is
annoying but OTOH if we retain it your regexp in the other patch
would match before and after..
Actually the best formatting IMHO would be to skip the ID altogether:
Action: Direct to RSS Context 1 (queue base offset: 2)
So please respin this, either set the ID to upper case or skip it.
And depending on the decision here respin the test (feel free to
repost before 24h passes, if you do).
next prev parent reply other threads:[~2024-11-12 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 19:05 [PATCH ethtool-next v2] rxclass: Make output for RSS context action explicit Daniel Xu
2024-11-11 19:27 ` Joe Damato
2024-11-12 10:03 ` Edward Cree
2024-11-12 15:40 ` Jakub Kicinski [this message]
2024-11-13 1:31 ` Daniel Xu
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=20241112074047.44490c6e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dxu@dxuuu.xyz \
--cc=ecree.xilinx@gmail.com \
--cc=jdamato@fastly.com \
--cc=kernel-team@meta.com \
--cc=martin.lau@linux.dev \
--cc=mkubecek@suse.cz \
--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).