From: Alasdair G Kergon <agk@redhat.com>
To: device-mapper development <dm-devel@redhat.com>,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [dm-devel] [PATCH] improve atomicity of device creation
Date: Tue, 11 Dec 2007 17:03:52 +0000 [thread overview]
Message-ID: <20071211170352.GS22311@agk.fab.redhat.com> (raw)
In-Reply-To: <1197391333.25082.31.camel@quest>
On Tue, Dec 11, 2007 at 04:42:13PM +0000, Scott James Remnant wrote:
> What is that agreed design?
In simple terms:
- udev takes over full responsibility for creating nodes
[this will probably be a ./configure option]
- udev provides interface we use to wait until it has finished
processing all the outstanding requests we sent it.
Key point is that our udev requests appear in batches, then we wait for
the batch to complete, as when the system is under memory pressure, udev
userspace may find itself blocked processing the first of the batch
until just before we issue the wait at the end of the batch.
[Note how libdevmapper today pushes all the requests onto an internal
stack and processes them all together at the end.]
Alasdair
--
agk@redhat.com
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-12-11 17:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 16:08 [PATCH] improve atomicity of device creation Scott James Remnant
2007-12-11 16:25 ` [dm-devel] " Alasdair G Kergon
2007-12-11 16:42 ` Scott James Remnant
2007-12-11 17:03 ` Alasdair G Kergon [this message]
2007-12-11 17:18 ` Scott James Remnant
2007-12-11 17:51 ` Kay Sievers
2007-12-11 18:08 ` Alasdair G Kergon
2007-12-11 18:25 ` Kay Sievers
2007-12-11 19:13 ` Alasdair G Kergon
2007-12-11 19:43 ` Alasdair G Kergon
2007-12-11 17:35 ` Kay Sievers
2007-12-11 17:40 ` Scott James Remnant
2007-12-11 17:53 ` Alasdair G Kergon
2007-12-11 19:09 ` Scott James Remnant
2007-12-11 18:03 ` Kay Sievers
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=20071211170352.GS22311@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
/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).