mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: zihan zhou <15645113830zzh@gmail.com>
To: vincent.guittot@linaro.org
Cc: 15645113830zzh@gmail.com, bsegall@google.com,
	dietmar.eggemann@arm.com, jameshongleiwang@126.com,
	juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
	mgorman@suse.de, mingo@redhat.com, peterz@infradead.org,
	rostedt@goodmis.org, vschneid@redhat.com, yaowenchao@jd.com,
	yaozhenguo@jd.com
Subject: Re: [PATCH V2] sched: Forward deadline for early tick
Date: Tue, 21 Jan 2025 10:46:01 +0800	[thread overview]
Message-ID: <20250121024600.109605-1-15645113830zzh@gmail.com> (raw)
In-Reply-To: <CAKfTPtD=OB9i1SZHE1bbmP23shVkrDj52K_V-5KByh3hDJJbcg@mail.gmail.com>

> > Just FYI. I think Vincent meant this one 2cf9ac40073d ("sched/fair:
> > Encapsulate set custom slice in a __setparam_fair() function"). You can
> > check it at the sched/core branch here:
> > https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/?h=sched/core&id=2cf9ac40073ddb6a70dd5ef94f1cf45501b696ed
> 
> You can find the information in MAINTAINERS file at the scheduler
> section. Actually it's
> 
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core

Thank you Vincent, thank you Honglei, I have learned it!

  reply	other threads:[~2025-01-21  2:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25  5:40 zihan zhou
2025-01-02 10:00 ` Vincent Guittot
2025-01-09  5:48   ` zihan zhou
2025-01-14 10:16     ` Vincent Guittot
2025-01-16  8:12       ` zihan zhou
2025-01-17  8:18         ` Vincent Guittot
2025-01-20  7:38           ` zihan zhou
2025-01-20 11:42             ` Honglei Wang
2025-01-20 13:39               ` Vincent Guittot
2025-01-21  2:46                 ` zihan zhou [this message]
2025-01-17 11:38 [PATCH V1] sched/debug: change "runnable tasks" to "Tasks on cpu" on sched debug Peter Zijlstra
2025-01-20  7:44 ` [PATCH V2] sched: Forward deadline for early tick zihan zhou
2025-01-20  7:55   ` zihan zhou

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=20250121024600.109605-1-15645113830zzh@gmail.com \
    --to=15645113830zzh@gmail.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jameshongleiwang@126.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    --cc=yaowenchao@jd.com \
    --cc=yaozhenguo@jd.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
all inboxes | Powered by JetHome®