All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: Luo Gengkun <luogengkun@huaweicloud.com>,
	peterz@infradead.org,  mingo@redhat.com, juri.lelli@redhat.com,
	vincent.guittot@linaro.org,  yu.c.chen@intel.com,
	kprateek.nayak@amd.com
Cc: dietmar.eggemann@arm.com, rostedt@goodmis.org,
	bsegall@google.com,  mgorman@suse.de, vschneid@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v11 1/2] sched/cache: Reduce the overhead of task_cache_work by only scan the visisted cpus
Date: Tue, 17 Nov 2026 10:27:06 -0800	[thread overview]
Message-ID: <1989e04ee420925b88ec5f17c6fbd11f06739ffd.camel@linux.intel.com> (raw)
In-Reply-To: <e2a78b9560fc0a232f3c7bd21e7d9738c5915ce1.camel@linux.intel.com>

On Mon, 2026-11-16 at 15:38 -0800, Tim Chen wrote:
> On Wed, 2026-11-11 at 11:04 +0000, Luo Gengkun wrote:
> 
> Nit:
> 
> subject would read better as
> 
> Reduce the overhead of task_cache_work() by scanning only the visited cpuswh

Typo.  I meant

Reduce the overhead of task_cache_work() by scanning only the visited cpus

Tim


  reply	other threads:[~2026-11-17 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 11:04 [PATCH v11 0/2] Cache aware scheduling: Reduce the overhead of task_cache_work Luo Gengkun
2026-11-11 11:04 ` [PATCH v11 1/2] sched/cache: Reduce the overhead of task_cache_work by only scan the visisted cpus Luo Gengkun
2026-11-16  7:24   ` Chen Yu
2026-11-16 23:38   ` Tim Chen
2026-11-17 18:27     ` Tim Chen [this message]
2026-11-11 11:04 ` [PATCH v11 2/2] -- DO NOT APPLY!!! -- sched/cache/debug: Add trace event and sched feature to track scan cost Luo Gengkun

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=1989e04ee420925b88ec5f17c6fbd11f06739ffd.camel@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luogengkun@huaweicloud.com \
    --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=yu.c.chen@intel.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.