All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <dmarkh@cfl.rr.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
	linux-kernel-rt <linux-rt-users@vger.kernel.org>
Cc: Max Krasnyanskiy <maxk@qualcomm.com>
Subject: processor isolation inquiry
Date: Sun, 21 Dec 2008 09:53:32 -0500	[thread overview]
Message-ID: <494E586C.7070107@cfl.rr.com> (raw)

It's been some time now since Max K. brought up the complete processor isolation
discussion. I know his original patch was NAK'd but some work on this was put
into cpusets. I'm unclear as to what actually has been or will be implemented.

The 2 things I'm most interested in are work queues, and local timer interrupts.
Is it yet possible to isolate a processor from either of these 2 things with
recent kernels?

The kernel doc concerning cpusets doesn't seem to clarify this for me.

The Process shielding instructions at

http://rt.wiki.kernel.org/index.php/CPU_shielding_using_/proc_and_/dev/cpuset

don't seem to help with work queues or local timer interrupts. Should they?

Thanks in advance for any pointers
Mark


                 reply	other threads:[~2008-12-21 16:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=494E586C.7070107@cfl.rr.com \
    --to=dmarkh@cfl.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=maxk@qualcomm.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.