public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Qiliang Yuan <realwujing@gmail.com>
To: longman@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 01/12] sched/isolation: Use cases for fine-grained isolation
Date: Mon, 20 Apr 2026 17:22:49 +0800	[thread overview]
Message-ID: <20260420092250.242319-1-realwujing@gmail.com> (raw)
In-Reply-To: <20260413192546.123987-1-longman@redhat.com>

Hi Waiman,

On Mon, 13 Apr 2026 15:25:46 -0400, Waiman Long wrote:
> Usually, if we want to run a latency sensitive workload like DPDK, we 
> try to minimize all sorts of kernel noises or interference as much as 
> possible. Do you have a good use case where it is advantageous to remove 
> some types of kernel noises from a given set of CPUs but not the others?

The initial intent for fine-grained control was to allow RCU callback
processing to remain local on specific CPUs to mitigate grace-period
stalls on large NUMA systems.

However, I agree that for typical DPDK use cases, simplified full isolation
is preferred to reduce complexity. In v3, I will pivot to a unified
isolation state. The primary value we aim to provide is the ability to
transition CPUs into this state dynamically via cgroups, which eliminates
the need for GRUB-based reboots and allows us to deploy latency-critical
services without interrupting existing workloads.

Best regards,
Qiliang

           reply	other threads:[~2026-04-20  9:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20260413192546.123987-1-longman@redhat.com>]

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=20260420092250.242319-1-realwujing@gmail.com \
    --to=realwujing@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.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