| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4640EF6B.6040701@s5r6.in-berlin.de> Date: Tue, 08 May 2007 23:45:15 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: david@...g.hm CC: Cornelia Huck <cornelia.huck@...ibm.com>, Linus Torvalds <torvalds@...ux-foundation.org>, Adrian Bunk <bunk@...sta.de>, Greg K-H <greg@...ah.com>, linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: Please revert 5adc55da4a7758021bcc374904b0f8b076508a11 (PCI_MULTITHREAD_PROBE) david@...g.hm wrote: > I have used userspace tools for managing multiple machines that spawn > tasks in parallel on multiple machines and then buffers them per-machine > to display the output of the commands in order, no matter which one > finished first. > > for example 'dsh m1,m2 ls /' would always result in > > m1 . > m1 .. > . > . > m2 . > m2 .. > . > . > > even if m2 finished before m1 > > why can't the detection be done in parallel, but the regestration of > detected devices be done in order? Userspace would have to tell the kernel which set of devices is available. (In your example: The set consists of m1 and m2; but does not include m0 nor m3 nor m6391.) So instead of telling the kernel beforehand what to enqueue for registration and in which order to enqueue it, we simply let userspace give persistent alias names to devices after the fact. -- Stefan Richter -=====-=-=== -=-= -=--- http://arcgraph.de/sr/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists