From: "rae l" <crquan@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: viro@zeniv.linux.org.uk, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, emdow@us.ibm.com
Subject: Re: [PATCH] PROC_FS: get and set the smp affinity of tasks by read-write /proc/<pid>/smp_affinity
Date: Thu, 10 Jan 2008 10:25:26 +0800 [thread overview]
Message-ID: <91b13c310801091825q5d763ff8if6463edba0c9e587@mail.gmail.com> (raw)
In-Reply-To: <20080109163350.79a4c346.akpm@linux-foundation.org>
On Jan 10, 2008 8:33 AM, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 4 Jan 2008 15:03:41 +0800
> Denis Cheng <crquan@gmail.com> wrote:
>
> > this adds a read-write /proc/<pid>/smp_affinity entry,
> > just like what /proc/irq/<irq>/smp_affinity does,
> > so now we can get and set the affinity of tasks by procfs,
> > this is especially useful used in shell scripts.
> >
> > this also adds a read-write /proc/<pid>/tasks/<tid>/smp_affinity
> > for the same purpose.
>
> Why not use /usr/bin/taskset?
I know /usr/bin/tasklet is another way to set smp affinity of a task,
it uses the sched_{set,get}affinity system call binary interface, but
add a /proc/<pid>/smp_affinity could give a new choice; and this keeps
consistency with /proc/irq/<irq>/smp_affinity, will be familiar to
most people.
Another way, the sysctl system call binary interface has been marked
deprecated recently, only /proc/sys/ operating interface left; I
wonder this this would be a tendency of virtual filesystem interface
to replace binary interface? In my opinion, vfs text interface is
always better than system call binary interface.
>
--
Denis Cheng
prev parent reply other threads:[~2008-01-10 2:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-04 7:03 Denis Cheng
2008-01-04 7:39 ` Paul Jackson
2008-01-04 7:54 ` Paul Jackson
2008-01-04 15:38 ` rae l
2008-01-04 19:13 ` Paul Jackson
2008-01-10 0:33 ` Andrew Morton
2008-01-10 2:25 ` rae l [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=91b13c310801091825q5d763ff8if6463edba0c9e587@mail.gmail.com \
--to=crquan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=emdow@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®