linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Karthik Singaram Lakshmanan" <karthiksingaram@gmail.com>
To: linux-rt-users@vger.kernel.org
Subject: Re: Question regarding sched_setaffinity
Date: Mon, 8 Sep 2008 10:40:01 -0400	[thread overview]
Message-ID: <1ca41c0f0809080740s20aadd48wa9486ce08f766e40@mail.gmail.com> (raw)
In-Reply-To: <48C51A63.1070700@compro.net>

Thanks for all your prompt replies. I really appreciate your help. I
was able to build some test programs to verify the behavior, I wanted
to make sure that I am not missing any corner cases. In my target
scenario, we do not consider taking CPUs offline, therefore
sched_setaffinity works perfectly fine.

Thanks,
Karthik

      reply	other threads:[~2008-09-08 14:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-01  3:12 Question regarding sched_setaffinity Karthik Singaram Lakshmanan
2008-09-05 19:24 ` Steven Rostedt
2008-09-05 20:04   ` Mark Hounschell
2008-09-05 20:28     ` Steven Rostedt
2008-09-05 20:45     ` Steven Rostedt
2008-09-08 12:28       ` Mark Hounschell
2008-09-08 14:40         ` Karthik Singaram Lakshmanan [this message]

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=1ca41c0f0809080740s20aadd48wa9486ce08f766e40@mail.gmail.com \
    --to=karthiksingaram@gmail.com \
    --cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).