Netdev List
 help / color / mirror / Atom feed
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 net-next] selftests: devmem: configure HDS threshold
Date: Mon, 30 Jun 2025 08:09:46 -0700	[thread overview]
Message-ID: <aGKouujd9Y18lmQw@mini-arch> (raw)
In-Reply-To: <20250630092818.1449599-1-ap420073@gmail.com>

On 06/30, Taehee Yoo wrote:
> The devmem TCP requires the hds-thresh value to be 0, but it doesn't
> change it automatically.
> Therefore, configure_hds_thresh() is added to handle this.
> 
> The run_devmem_tests() now tests hds_thresh, but it skips test if the
> hds_thresh_max value is 0.
> 
> Signed-off-by: Taehee Yoo <ap420073@gmail.com>
> ---
>  .../selftests/drivers/net/hw/ncdevmem.c       | 86 +++++++++++++++++++
>  1 file changed, 86 insertions(+)
> 
> diff --git a/tools/testing/selftests/drivers/net/hw/ncdevmem.c b/tools/testing/selftests/drivers/net/hw/ncdevmem.c
> index cc9b40d9c5d5..d78b5e5697d7 100644
> --- a/tools/testing/selftests/drivers/net/hw/ncdevmem.c
> +++ b/tools/testing/selftests/drivers/net/hw/ncdevmem.c
> @@ -349,6 +349,72 @@ static int configure_headersplit(bool on)
>  	return ret;
>  }
>  
> +static int configure_hds_thresh(int len)
> +{
> +	struct ethtool_rings_get_req *get_req;
> +	struct ethtool_rings_get_rsp *get_rsp;
> +	struct ethtool_rings_set_req *req;
> +	struct ynl_error yerr;
> +	struct ynl_sock *ys;
> +	int ret;
> +
> +	ys = ynl_sock_create(&ynl_ethtool_family, &yerr);
> +	if (!ys) {
> +		fprintf(stderr, "YNL: %s\n", yerr.msg);
> +		return -1;
> +	}
> +
> +	req = ethtool_rings_set_req_alloc();
> +	ethtool_rings_set_req_set_header_dev_index(req, ifindex);

[..]

> +	ethtool_rings_set_req_set_hds_thresh(req, len);

Any reason not to add this to the existing configure_headersplit? Is it
only for tests?

  reply	other threads:[~2025-06-30 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-30  9:28 [PATCH net-next] selftests: devmem: configure HDS threshold Taehee Yoo
2025-06-30 15:09 ` Stanislav Fomichev [this message]
2025-07-01  3:05   ` Taehee Yoo
2025-06-30 16:11 ` Mina Almasry
2025-07-01  3:11   ` Taehee Yoo

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=aGKouujd9Y18lmQw@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