From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Greg KH <greg@kroah.com>, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: PATCH: Multiprobe sanitizer
Date: Thu, 17 Aug 2006 09:41:00 +0100 [thread overview]
Message-ID: <1155804060.15195.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1155797833.11312.160.camel@localhost.localdomain>
Ar Iau, 2006-08-17 am 08:57 +0200, ysgrifennodd Benjamin Herrenschmidt:
> In fact, I'm all about making the problem worse by agressively
> paralellilizing everything to get distros config mecanisms to catch up
> and stop using the interface name (or use ifrename).
I'm so glad I don't have to depend on your code then because I have to
actually deal with the real world not try to commit design suicide in
pursuit in of elegance.
There are numerous cases where bus stability happens to matter because
you cannot identify the different devices. The disk and ethernet cases
are relatively managable (disk has some distribution issues with fstab
etc on older setups). Things get nasty when you look at say sound or
video.
A classic example would be a typical security system with four identical
PCI video capture cards. There is no way other than PCI bus ordering to
order them, and if you don't order them your system isn't useful as you
do different processing on different camera streams.
>From a performance perspective the only one we really care about is
probably disks. Even there we need some kind of ordering (or ability to
order) so that we can handle unlabelled (eg new) volumes and md
components.
Right now lvm/dm/md all depend on real disk names to be useful on large
systems because the time to scan for labels is too high. On small
systems some tools work ok although not all with labels.
Disk has another awkward problem too - power control and management.
next prev parent reply other threads:[~2006-08-17 8:21 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 [this message]
2006-08-17 9:24 ` Benjamin Herrenschmidt
2006-08-17 12:00 ` Greg KH
2006-08-17 12:12 ` Benjamin Herrenschmidt
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=1155804060.15195.30.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--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®