[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 4/5] Fix loop test

From: Phillip Susi
Subject: Re: [PATCH 4/5] Fix loop test
Date: Thu, 22 Dec 2011 20:07:06 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 Thunderbird/8.0

Hash: SHA1

On 12/22/2011 04:54 PM, Jim Meyering wrote:
> I'd really like to have a way to run two or more scsi_debug-using
> tests in parallel but that is not possible: the kernel allows only one.
> Note that for many of our scsi-debug-using tests, you cannot duplicate
> the functionality using a loop device.  Besides, even where you can,

I thought the only reason you needed scsi_debug was because loop devices 
couldn't be partitioned.  What other reason is there?  

> because we don't use e.g., special alignment or block size, you risk
> being unable to create a loop device due to inherent limitations, or,
> if you create a few because their tests are running in parallel, you
> risk perturbing regular processes that (albeit rarely) need to create a
> loop device.  That is part of the reason for my using a private-homed
> device tree: there I know I'm starting from a clean slate: i.e., far
> less risk of interfering with some other loop-creating process.

I don't follow.  How does using loop devices interfere with other processes 
doing the same?  And how does using your own /dev directory help at all?  Just 
because you have your own /dev directory doesn't mean you have your own set of 
devices; any devices that actually exist when you start still exist ( and are 
in use ) so you can't re-create a private copy, and any devices you create 
still show up in the real /dev.
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


reply via email to

[Prev in Thread] Current Thread [Next in Thread]