From: Mike Galbraith <umgwanakikbuti-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Viresh Kumar <viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org,
fweisbec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org,
linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org,
linaro-networking-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
Arvind.Chauhan-5wv7dgnIgG8@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH V2 0/8] cpusets: Isolate CPUs via sysfs using cpusets
Date: Sun, 06 Apr 2014 10:30:20 +0200 [thread overview]
Message-ID: <1396773020.11763.17.camel@marge.simpson.net> (raw)
In-Reply-To: <cover.1396599474.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
On Fri, 2014-04-04 at 14:05 +0530, Viresh Kumar wrote:
> We need to migrate away all the background kernel activities (Unbound) for
> systems requiring isolation of cores (HPC, Real time, networking, etc). After
> creating cpusets, you can write 1 or 0 to cpuset.quiesce file.
I wonder if adding a quiesce switch is really necessary.
Seems to me that if you don't have load balancing turned off, you can't
be very concerned about perturbation, so this should be tied into the
load balancing on/off switch as an extension to isolating cores from the
#1 perturbation source, the scheduler.
I also didn't notice a check for is_cpu_exclusive() at a glance, which
would be a bug, but one that would go away if this additional isolation
were coupled to the existing isolation switch.
-Mike
next prev parent reply other threads:[~2014-04-06 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 8:35 [PATCH V2 0/8] cpusets: Isolate CPUs via sysfs using cpusets Viresh Kumar
2014-04-04 8:35 ` [PATCH V2 1/8] timer: track pinned timers with TIMER_PINNED flag Viresh Kumar
[not found] ` <cover.1396599474.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-04-04 8:35 ` [PATCH V2 2/8] timer: don't migrate pinned timers Viresh Kumar
2014-04-04 8:35 ` [PATCH V2 3/8] timer: create timer_quiesce_cpu() to isolate CPU from timers Viresh Kumar
2014-04-04 8:35 ` [PATCH V2 4/8] hrtimer: update timer->state with 'pinned' information Viresh Kumar
2014-04-06 8:30 ` Mike Galbraith [this message]
2014-04-07 4:11 ` [PATCH V2 0/8] cpusets: Isolate CPUs via sysfs using cpusets Viresh Kumar
[not found] ` <CAKohpomW3jpQEqFxD3m_br8GchJyq9-KSxW2x7JLCRqDgf4SAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-04-07 5:04 ` Mike Galbraith
[not found] ` <1396847090.5218.9.camel-YqMYhexLQo31wTEvPJ5Q0F6hYfS7NtTn@public.gmane.org>
2014-04-07 5:17 ` Viresh Kumar
2014-04-04 8:35 ` [PATCH V2 5/8] hrtimer: don't migrate pinned timers Viresh Kumar
2014-04-04 8:35 ` [PATCH V2 6/8] hrtimer: create hrtimer_quiesce_cpu() to isolate CPU from hrtimers Viresh Kumar
2014-04-04 8:35 ` [PATCH V2 7/8] cpuset: Create sysfs file: cpusets.quiesce to isolate CPUs Viresh Kumar
2014-04-04 8:35 ` [PATCH V2 8/8] sched: don't queue timers on quiesced CPUs Viresh Kumar
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=1396773020.11763.17.camel@marge.simpson.net \
--to=umgwanakikbuti-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Arvind.Chauhan-5wv7dgnIgG8@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=fweisbec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linaro-kernel-cunTk1MwBs8s++Sfvej+rw@public.gmane.org \
--cc=linaro-networking-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lizefan-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=peterz-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
/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