The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Paul Jackson <pj@sgi.com>
Cc: Simon.Derr@bull.net, ak@suse.de, linux-kernel@vger.kernel.org,
	clameter@sgi.com
Subject: Re: [PATCH 3/5] cpuset: change marker for relative numbering
Date: Sun, 6 Nov 2005 12:57:38 -0800	[thread overview]
Message-ID: <20051106125738.7e140f1c.akpm@osdl.org> (raw)
In-Reply-To: <20051106020410.2c0c26e1.pj@sgi.com>

Paul Jackson <pj@sgi.com> wrote:
>
> > Given that you're developing a library to do all this, why not do proper
>  > locking in userspace and require that all cpuset updates go via the
>  > library?
> 
>  The superficial reason why not is that I can't prevent someone from
>  doing "echo pid > /dev/cpuset/tasks", moving a task to another cpuset
>  even as that task in the middle of dorking with its cpusets.  Not all
>  cpuset operations will involve using my blessed library.

If someone modifies a library-managed cpuset via the backdoor then the
library (and its caller) are out of sync with reality _anyway_.  Why does
an encounter with this very small race window worsen things?

  reply	other threads:[~2005-11-06 20:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04  5:31 [PATCH 1/5] cpuset: better bitmap remap defaults Paul Jackson
2005-11-04  5:31 ` [PATCH 2/5] cpuset: rebind numa vma mempolicy Paul Jackson
2005-11-07  6:10   ` Paul Jackson
2005-11-04  5:31 ` [PATCH 3/5] cpuset: change marker for relative numbering Paul Jackson
2005-11-05  7:08   ` Andrew Morton
2005-11-06 10:04     ` Paul Jackson
2005-11-06 20:57       ` Andrew Morton [this message]
2005-11-06 22:49         ` Paul Jackson
2005-11-04  5:31 ` [PATCH 4/5] cpuset: mempolicy one more nodemask conversion Paul Jackson
2005-11-04  5:31 ` [PATCH 5/5] cpuset: memory reclaim rate meter Paul Jackson
2005-11-05  7:13   ` Andrew Morton
2005-11-05  7:34     ` Paul Jackson
2005-11-05  7:43     ` Paul Jackson
2005-11-05  7:27   ` Paul Jackson

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=20051106125738.7e140f1c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=Simon.Derr@bull.net \
    --cc=ak@suse.de \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox