From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alasdair G Kergon Date: Tue, 11 Dec 2007 17:03:52 +0000 Subject: Re: [dm-devel] [PATCH] improve atomicity of device creation Message-Id: <20071211170352.GS22311@agk.fab.redhat.com> List-Id: References: <1197389316.25082.27.camel@quest> <20071211162538.GR22311@agk.fab.redhat.com> <1197391333.25082.31.camel@quest> In-Reply-To: <1197391333.25082.31.camel@quest> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: device-mapper development , linux-hotplug-devel@lists.sourceforge.net 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