All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@intel.com>
To: Krystian Kaniewski <krystianmkaniewski@gmail.com>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Jiri Pirko <jiri@resnulli.us>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Simon Horman <horms@kernel.org>,
	Vladimir Oltean <vladimir.oltean@nxp.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	syzbot+e044a9b6370ed8ca9737@syzkaller.appspotmail.com
Subject: Re: [PATCH net v2 2/2] net/sched: taprio: do not replay missed entries in advance_sched()
Date: Tue, 03 Nov 2026 16:56:56 -0800	[thread overview]
Message-ID: <87bj85wh0n.fsf@intel.com> (raw)
In-Reply-To: <ff74c290-3093-49ec-85ce-0e2385419366@gmail.com>

Hi,

Krystian Kaniewski <krystianmkaniewski@gmail.com> writes:

> On 10/14/26 22:51, Vinicius Costa Gomes wrote:
>>>>> +	struct sched_entry *entry, *found = NULL;
>>>>> +	ktime_t cycle_start = sched->start_time;
>>>>> +	s64 offset, entry_end = 0, elapsed = 0;
>>>>> +
>>>>> +	if (ktime_after(now, cycle_start)) {
>>>>> +		s64 periods = div64_s64(ktime_sub(now, cycle_start),
>>>>> +					sched->period);
>>>>> +
>>>>> +		cycle_start = ktime_add_ns(cycle_start,
>>>>> +					   periods * sched->period);
>>>>> +	}
>>>>> +	offset = ktime_sub(now, cycle_start);
>>>>> +
>>>>> +	/* The offset is less than one period, so an entry which ends after
>>>>> +	 * @now is found at the latest at the entry which reaches the end of
>>>>> +	 * the cycle, or at the last entry. A schedule has at least one entry,
>>>>> +	 * so the loop always sets found.
>>>>> +	 */
>>>>> +	list_for_each_entry(entry, &sched->entries, list) {
>>>>> +		entry_end = min_t(s64, elapsed + entry->interval,
>>>>> +				  sched->cycle_time);
>>>>> +		if (offset < entry_end ||
>>>>> +		    list_is_last(&entry->list, &sched->entries)) {
>>>>> +			found = entry;
>>>>> +			break;
>>>>> +		}
>>>>> +		elapsed = entry_end;
>>>>> +	}
>>>>> +
>>>>> +	*start = ktime_add_ns(cycle_start, elapsed);
>>>>> +	*end = ktime_add_ns(cycle_start, entry_end);
>>>>> +	sched->cycle_end_time = ktime_add_ns(cycle_start,
>>>>> sched->cycle_time);
>>>>
>>>> Having this side effect here was unexpected. I think this would make
>>>> more sense outside this function.
>>>>
>>>
>>> Agreed. I can make taprio_entry_at() return the cycle end through an
>>> extra output argument and have advance_sched() store it explicitly in
>>> oper->cycle_end_time. The helper could then take the schedule as const.
>>>
>>> I can wait for the rest of your review of this patch before sending v3
>>>
>> 
>> I am going to try and review this by end of this week.
>> 
>> 
>> Cheers,
>
> Hi Vinicius,
>
> Just a gentle ping on patch 2/2. Did you have a chance to continue the
> review?


Sorry for the delay, just another minor/optional nitpick. The series
look good, run a couple of tests on a VM. For the series:

Acked-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>


> -- 
> Krystian Kaniewski

-- 
Vinicius

  reply	other threads:[~2026-11-04  0:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-09 12:33 [PATCH net v2 0/2] net/sched: taprio: fix RCU stall from replayed schedule entries Krystian Kaniewski
2026-10-09 12:33 ` [PATCH net v2 1/2] net/sched: taprio: reject software schedules that overflow their timestamps Krystian Kaniewski
2026-10-12 22:36   ` Vinicius Costa Gomes
2026-11-04  0:54   ` Vinicius Costa Gomes
2026-10-09 12:33 ` [PATCH net v2 2/2] net/sched: taprio: do not replay missed entries in advance_sched() Krystian Kaniewski
2026-10-12 22:53   ` Vinicius Costa Gomes
2026-10-14  9:08     ` Krystian Kaniewski
2026-10-14 20:51       ` Vinicius Costa Gomes
2026-11-02 10:19         ` Krystian Kaniewski
2026-11-04  0:56           ` Vinicius Costa Gomes [this message]
2026-11-04  9:09             ` Krystian Kaniewski

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=87bj85wh0n.fsf@intel.com \
    --to=vinicius.gomes@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=krystianmkaniewski@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=syzbot+e044a9b6370ed8ca9737@syzkaller.appspotmail.com \
    --cc=vladimir.oltean@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.