From: Nadia Derbey <Nadia.Derbey@bull.net>
To: Nick Andrew <nick@nick-andrew.net>
Cc: linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, orenl@cs.columbia.edu
Subject: Re: [RFC][PATCH 0/4] Object creation with a specified id
Date: Tue, 15 Apr 2008 12:30:26 +0200 [thread overview]
Message-ID: <480483C2.3030509@bull.net> (raw)
In-Reply-To: <20080415030623.GA8171@tull.net>
Nick Andrew wrote:
> On Fri, Apr 04, 2008 at 04:51:29PM +0200, Nadia.Derbey@bull.net wrote:
>
>> . echo "LONG XX" > /proc/self/next_id
>> next object to be created will have an id set to XX
>> . echo "LONG<n> X0 ... X<n-1>" > /proc/self/next_id
>> next object to be created will have its ids set to XX0, ... X<n-1>
>> This is particularly useful for processes that may have several ids if
>> they belong to nested namespaces.
>
>
> How do you handle race conditions, i.e. you specify the ID for the
> next object to be created, and then some other thread goes and creates
> an object before your thread creates one?
>
> Nick.
Sorry for not answering earlier, I just saw your e-mail!
It's true that the way I've done things, the "create_with_id" doesn't
take into account multi-threaded apps, since "self" is related to the
thread group leader.
May be using something like /proc/self/task/<my_tid>/next_id would be
better, but I have to think more about it...
Regards,
Nadia
next prev parent reply other threads:[~2008-04-15 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 14:51 Nadia.Derbey
2008-04-04 14:51 ` [RFC][PATCH 1/4] Provide a new procfs interface to set next id Nadia.Derbey
2008-04-04 14:51 ` [RFC][PATCH 2/4] Provide a new procfs interface to set next upid nr(s) Nadia.Derbey
2008-04-04 14:51 ` [RFC][PATCH 3/4] IPC: use the target ID specified in procfs Nadia.Derbey
2008-04-04 14:51 ` [RFC][PATCH 4/4] PID: " Nadia.Derbey
2008-04-15 3:06 ` [RFC][PATCH 0/4] Object creation with a specified id Nick Andrew
2008-04-15 10:30 ` Nadia Derbey [this message]
2008-04-15 18:52 ` Oren Laadan
2008-04-18 5:46 ` Nadia Derbey
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=480483C2.3030509@bull.net \
--to=nadia.derbey@bull.net \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@nick-andrew.net \
--cc=orenl@cs.columbia.edu \
/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
Powered by JetHome