-----BEGIN PGP SIGNED MESSAGE----- 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. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJO89Q6AAoJEJrBOlT6nu75FSAIALVmZYkn5LJF1zfVtZPNcNtB Tpa8XZuvyj5NTOEXIR/LaeulbYvw1ANZtP8dOaavPXXOtJtGkg5grxm9Qxe0JToZ soDWu6R/SAtyijHh2UTAG0XpWuB237ibLfQVw6MVWkKzN/+wjz9TY/hsnYhfZ1fP Mee5DoWar54xu4enq+Q5ATqCoHrpj9s+aOmD6pA+5XN7eiKu+Y//aTkoZGl++O5u Otc1rK3uWZ6GOjDytC+Bcj5LWGAUr8xSjy8ZgPQoFksja6PYyHuyBZbe/itwG4aQ DR/fNeevizh6xS3rVZhXjpPFGWnqJw1vZilsfYGJsW7Pm/yz8c5msa5udFImvMA= =TOWo -----END PGP SIGNATURE-----
