From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to prevent other processes from being scheduled
Date: Tue, 05 Nov 2013 14:30:35 -0500 [thread overview]
Message-ID: <18751.1383679835@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 06 Nov 2013 00:51:03 +0900." <527913E7.5030705@gmail.com>
On Wed, 06 Nov 2013 00:51:03 +0900, "J.Hwan Kim" said:
> How can I prevent other processes than my specific application from
> being scheduled?
What problem are you trying to solve by not allowing other processes
to run? There's almost certainly a better approach.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20131105/2e18844c/attachment.bin
next prev parent reply other threads:[~2013-11-05 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 15:51 How to prevent other processes from being scheduled J.Hwan Kim
2013-11-05 19:30 ` Valdis.Kletnieks at vt.edu [this message]
2013-11-06 5:16 ` Mulyadi Santosa
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=18751.1383679835@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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).