From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Greg KH <greg@kroah.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Multiprobe sanitizer
Date: Thu, 17 Aug 2006 14:12:57 +0200 [thread overview]
Message-ID: <1155816777.11312.177.camel@localhost.localdomain> (raw)
In-Reply-To: <20060817120013.GC6843@kroah.com>
On Thu, 2006-08-17 at 05:00 -0700, Greg KH wrote:
> On Thu, Aug 17, 2006 at 11:24:35AM +0200, Benjamin Herrenschmidt wrote:
> > Probe ordering is fragile and completely defeated with busses that are
> > already probed asynchronously (like USB or firewire), and things can
> > only get worse. Thus we need to look for generic solutions, the trick of
> > maintaining probe ordering will work around problems today but we'll
> > still hit the wall in an increasing number of cases in the future.
>
> That's exactly why udev was created :)
>
> It can handle bus ordering issues already today just fine, and distros
> use it this way in shipping, "enterprise ready" products.
Only up to a certain point and for certain drivers... but yeah. That's
probably the right direction to take. Now, I'll let you and Alan argue
wether it's sufficient or not to move toward a fully parallel probing :)
Ben.
next prev parent reply other threads:[~2006-08-17 12:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 16:42 Alan Cox
2006-08-16 22:26 ` Greg KH
2006-08-17 0:36 ` Alan Cox
2006-08-17 6:57 ` Benjamin Herrenschmidt
2006-08-17 7:00 ` Arjan van de Ven
2006-08-17 8:41 ` Alan Cox
2006-08-17 9:24 ` Benjamin Herrenschmidt
2006-08-17 12:00 ` Greg KH
2006-08-17 12:12 ` Benjamin Herrenschmidt [this message]
2006-08-17 12:22 ` Greg KH
2006-08-17 12:37 ` Benjamin Herrenschmidt
2006-08-17 13:04 ` Arjan van de Ven
2006-08-17 13:10 ` Benjamin Herrenschmidt
2006-08-17 15:44 ` Greg KH
2006-08-17 14:43 ` Olaf Hering
2006-08-17 15:42 ` Greg KH
2006-08-17 11:58 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1155816777.11312.177.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®