From: Stanislav Fomichev <stfomichev@gmail.com>
To: Taehee Yoo <ap420073@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, andrew+netdev@lunn.ch, shuah@kernel.org,
almasrymina@google.com, sdf@fomichev.me, jdamato@fastly.com,
netdev@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 net-next] selftests: devmem: configure HDS threshold
Date: Thu, 3 Jul 2025 08:41:02 -0700 [thread overview]
Message-ID: <aGakjsP3ya6mJE9V@mini-arch> (raw)
In-Reply-To: <CAMArcTVYyGWAY0B1mem2nosQk1sJsg5nq9Uz5qB-wa7MFsqt7g@mail.gmail.com>
On 07/03, Taehee Yoo wrote:
> On Thu, Jul 3, 2025 at 12:37 AM Stanislav Fomichev <stfomichev@gmail.com> wrote:
> >
>
> Hi Stanislav,
> Thanks a lot for your review!
>
> > On 07/02, Taehee Yoo wrote:
> > > The devmem TCP requires the hds-thresh value to be 0, but it doesn't
> > > change it automatically.
> > > Therefore, make configure_headersplit() sets hds-thresh value to 0.
> > >
> > > Signed-off-by: Taehee Yoo <ap420073@gmail.com>
> > > ---
> > >
> > > v2:
> > > - Do not implement configure_hds_thresh().
> > > - Make configure_headersplit() sets hds-thresh to 0.
> > >
> > > tools/testing/selftests/drivers/net/hw/ncdevmem.c | 11 ++++++++++-
> > > 1 file changed, 10 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/tools/testing/selftests/drivers/net/hw/ncdevmem.c b/tools/testing/selftests/drivers/net/hw/ncdevmem.c
> > > index cc9b40d9c5d5..52b72de11e3b 100644
> > > --- a/tools/testing/selftests/drivers/net/hw/ncdevmem.c
> > > +++ b/tools/testing/selftests/drivers/net/hw/ncdevmem.c
> > > @@ -331,6 +331,12 @@ static int configure_headersplit(bool on)
> > > ret = ethtool_rings_set(ys, req);
> > > if (ret < 0)
> > > fprintf(stderr, "YNL failed: %s\n", ys->err.msg);
> > > + if (on) {
> > > + ethtool_rings_set_req_set_hds_thresh(req, 0);
> > > + ret = ethtool_rings_set(ys, req);
> >
> > Why call ethtool_rings_set again here? Can we move ethtool_rings_set_req_set_hds_thresh
> > to be after ethtool_rings_set_req_set_tcp_data_split ?
>
> I think tcp-data-split will fail if a driver doesn't support
> hds-thresh, even if it supports tcp-data-split.
> So, I separated them.
Sorry for going back and forth on this, but in this case your v1 is
better (maybe improve it by not printing an error for 'not supported'
errno). And will probably better be suited for Jakub's suggestion of
adding undo.
next prev parent reply other threads:[~2025-07-03 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 10:42 [PATCH v2 net-next] selftests: devmem: configure HDS threshold Taehee Yoo
2025-07-02 15:37 ` Stanislav Fomichev
2025-07-02 16:12 ` Taehee Yoo
2025-07-03 15:41 ` Stanislav Fomichev [this message]
2025-07-02 18:39 ` Jakub Kicinski
2025-07-03 3:51 ` Taehee Yoo
2025-07-07 18:48 ` Mina Almasry
2025-07-07 20:10 ` Jakub Kicinski
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=aGakjsP3ya6mJE9V@mini-arch \
--to=stfomichev@gmail.com \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=ap420073@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdamato@fastly.com \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@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).