public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Xin Zhao <jackzxcui1989@163.com>,
	 willemdebruijn.kernel@gmail.com,  edumazet@google.com,
	 ferenc@fejes.dev
Cc: davem@davemloft.net,  kuba@kernel.org,  pabeni@redhat.com,
	 horms@kernel.org,  netdev@vger.kernel.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: af_packet: Use hrtimer to do the retire operation
Date: Sun, 17 Aug 2025 11:55:37 -0400	[thread overview]
Message-ID: <willemdebruijn.kernel.157558f062bfc@gmail.com> (raw)
In-Reply-To: <20250817144709.3599024-1-jackzxcui1989@163.com>

Xin Zhao wrote:
> On Sun, 2025-08-17 at 21:28 +0800, Willem wrote:
> 
> > Here we cannot use hrtimer_add_expires for the same reason you gave in
> > the second version of the patch:
> > 
> > > Additionally, I think we cannot avoid using ktime_get, as the retire
> > > timeout for each block is not fixed. When there are a lot of network packets,
> > > a block can retire quickly, and if we do not re-fetch the time, the timeout
> > > duration may be set incorrectly.
> > 
> > Is that right?
> > 
> > Otherwise patch LGTM.
> 
> 
> I'll think about whether there's a better way to implement the logic.
> 
> Additionally, regarding the previous email where you mentioned replacing retire_blk_tov
> with the interval_ktime field, do we still need to make that change?
> I noticed you didn't respond to my latest patch that replaces retire_blk_tov with
> interval_ktime, and I'm wondering if we should make that change.
> So we remain the retire_blk_tov field?

Sorry, this response was intended to v4. Yes, let's keep that change.
If hrtimer_add_expires cannot be used, then that patch is good as is.

  reply	other threads:[~2025-08-17 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-17 14:47 [PATCH net-next v3] net: af_packet: Use hrtimer to do the retire operation Xin Zhao
2025-08-17 15:55 ` Willem de Bruijn [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-18  7:13 Xin Zhao
2025-08-18  9:21 ` Willem de Bruijn
2025-08-18  5:38 Xin Zhao
2025-08-18  7:21 ` Willem de Bruijn
2025-08-16 17:01 Xin Zhao
2025-08-16  2:48 Xin Zhao
2025-08-16  9:34 ` Willem de Bruijn
2025-08-17 13:28 ` Willem de Bruijn

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=willemdebruijn.kernel.157558f062bfc@gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ferenc@fejes.dev \
    --cc=horms@kernel.org \
    --cc=jackzxcui1989@163.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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