public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: yang.yang29@zte.com.cn, mingo@redhat.com, axboe@kernel.dk,
	tj@kernel.org, hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
	juri.lelli@redhat.com
Subject: Re: [RESEND PATCH linux-next] sched/psi: avoid resetting the min update period when it is unnecessary
Date: Sat, 13 May 2023 11:45:08 +0200	[thread overview]
Message-ID: <20230513094508.GC4253@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAJuCfpEC67SBGFSCOD9TykwE_BR2ax5+T4XUKhq_U=qBJttMgw@mail.gmail.com>

On Fri, May 12, 2023 at 10:56:02AM -0700, Suren Baghdasaryan wrote:
> On Fri, May 12, 2023 at 1:42 AM <yang.yang29@zte.com.cn> wrote:
> >
> > From: Yang Yang <yang.yang29@zte.com.cn>
> >
> > Psi_group's poll_min_period is determined by the minimum window size of
> > psi_trigger when creating new triggers. While destroying a psi_trigger, there
> > is no need to reset poll_min_period if the psi_trigger being destroyed did not
> > have the minimum window size, since in this condition poll_min_period will
> > remain the same as before.
> >
> > Signed-off-by: Yang Yang <yang.yang29@zte.com.cn>
> > Acked-by: Suren Baghdasaryan <surenb@google.com>
> 
> Hi Peter,
> This is another psi-related patch that slipped through the cracks.
> Could you please take it into your tree? The original one [1] had a
> different title but the same code.

It does not cleanly apply to tip/sched/core; could either of you rebase
please?

Thanks!

  reply	other threads:[~2023-05-13  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12  8:42 [RESEND PATCH linux-next] sched/psi: avoid resetting the min update period when it is unnecessary yang.yang29
2023-05-12 17:56 ` Suren Baghdasaryan
2023-05-13  9:45   ` Peter Zijlstra [this message]
2023-05-14 16:36     ` Suren Baghdasaryan

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=20230513094508.GC4253@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=hannes@cmpxchg.org \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=surenb@google.com \
    --cc=tj@kernel.org \
    --cc=yang.yang29@zte.com.cn \
    /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