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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <457C7D8D.7090703@f2s.com>
Date:	Sun, 10 Dec 2006 21:35:09 +0000
From:	Ian Molton <spyro@....com>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Luke Kenneth Casson Leighton <lkcl@...l.net>,
	kernel-discuss@...dhelds.org, linux-kernel@...r.kernel.org,
	Jiri Kosina <jikos@...os.cz>
Subject: Re: [Kernel-discuss] Re: parallel boot device initialisation	(kernel-space
 not userspace)

Stefan Richter wrote:
> Luke Kenneth Casson Leighton wrote:

> Your thought to pick one subsystem and implement multithreaded probing is
> exactly the way to go. If the subsystem is already properly using the
> driver core, part of what's needed is already in place. You "merely" have
> to look out for proper access to shared resources, and maybe synchronization
> of the final step in initialization... (Like in case of the SCSI subsystem.
> People usually want to wait for all scanning threads to finish before the
> system proceeds to mount filesystems.)

Would love to see this happen to platform devices...

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ