All of lore.kernel.org
 help / color / mirror / Atom feed
From: KobaK <kobak@nvidia.com>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Chen Yu <yu.c.chen@intel.com>,
	Ricardo Neri <ricardo.neri@intel.com>,
	Len Brown <len.brown@intel.com>, Aubrey Li <aubrey.li@intel.com>,
	linux-kernel@vger.kernel.org,
	Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Subject: Re: [PATCH] sched/fair: avoid creating misfits during cache-aware balancing
Date: Mon, 14 Sep 2026 10:59:49 +0800	[thread overview]
Message-ID: <20260914025949.1348528-1-kobak@nvidia.com> (raw)
In-Reply-To: <20260825174112.2580942-1-tim.c.chen@linux.intel.com>

Hi Tim,

Thanks for the cache-aware load-balancing misfit patch. The tradeoff
you describe (LLC locality vs capacity loss) is clear.

I have been trying to understand how this showed up in testing. The
cover explains the failure mode, but I did not find a note on the
observation method.

Would you mind sharing how you tested and observed it? In particular:
which hybrid generation, what workload, and whether you used
schedstat lb_imbalance_misfit or another signal.

Thanks,
Koba

  parent reply	other threads:[~2026-09-14  2:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-25 17:41 [PATCH] sched/fair: avoid creating misfits during cache-aware balancing Tim Chen
2026-08-26 15:57 ` Tim Chen
2026-08-31  8:41 ` Peter Zijlstra
2026-08-31 17:17   ` Tim Chen
2026-08-31 17:40   ` Tim Chen
2026-09-02  7:21     ` [tip: sched/urgent] sched/fair: Avoid " tip-bot2 for Tim Chen
2026-09-14  2:59 ` KobaK [this message]
2026-09-14 19:51   ` [PATCH] sched/fair: avoid " Tim Chen

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=20260914025949.1348528-1-kobak@nvidia.com \
    --to=kobak@nvidia.com \
    --cc=aubrey.li@intel.com \
    --cc=kprateek.nayak@amd.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ricardo.neri-calderon@linux.intel.com \
    --cc=ricardo.neri@intel.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=vincent.guittot@linaro.org \
    --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.