All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ragnar Kjørstad" <kernel@ragnark.vestdata.no>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first
Date: Sat, 9 Sep 2006 16:37:44 +0200	[thread overview]
Message-ID: <20060909143744.GZ16876@vestdata.no> (raw)

[ I'm not subscribed. Please CC me on replies ]

> Solution:
> 
> The solution can come in multiple steps.
> 
> Suggested fix #1: kernel
> Patch below sorts the two device lists into breadth-first ordering to
> maintain compatibility with 2.4 kernels.  It also overloads the
> 'pci=nosort' option to disable the breadth-first sort (and on i386 it
> continues to disable the pcibios_find_device sort as well).

As far as I understand it's difficult to argue that sorting the devices
one way is more "correct" than the other, so your argument is basically:
1) Compability with 2.4
2) Consistency with BIOS and external labels.

Both are important, but the problem is
1) Compability with 2.4 means breaking compability with previous
   2.6 kernels. And 2.6 has been out long enough that it's more
   important than 2.4.
2) There is also hardware where the 2.6 behaviour is consistent with
   BIOS and external labels where 2.4 is not.

An _option_ to enable 2.4 compatible device ordering on the other hand
would have just advantages, no disadvantages.


-- 
Ragnar Kjørstad
Software Engineer
Scali - http://www.scali.com
Scaling the Linux Datacenter

             reply	other threads:[~2006-09-09 14:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09 14:37 Ragnar Kjørstad [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-08 19:34 [PATCH 2.6.18-rc5] PCI: sort device lists breadth-first Matt Domsch
2006-09-08  3:18 Matt Domsch
2006-09-08  3:14 Matt Domsch
2006-09-08 15:56 ` Dave Jones
2006-09-08 16:18   ` Matt Domsch
2006-09-08 16:55     ` Arjan van de Ven
2006-09-11 19:36       ` Bill Davidsen
2006-09-12  3:08         ` Matt Domsch
2006-09-12 21:06           ` Bill Davidsen
2006-09-08 16:45   ` Greg KH
2006-09-08 18:20 ` Andrew Morton
2006-09-08 18:52   ` Matt Domsch
2006-09-08 18:59   ` Alexey Dobriyan
2006-09-09  9:05   ` Jeff Garzik
2006-09-09 12:11     ` Pavel Machek
2006-09-10 11:26       ` Stefan Richter
2006-09-10 13:02     ` Greg KH
2006-09-15  3:53 ` Dan Carpenter
2006-09-15 13:02   ` Matt Domsch
2006-09-16  2:39     ` Dan Carpenter

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=20060909143744.GZ16876@vestdata.no \
    --to=kernel@ragnark.vestdata.no \
    --cc=Matt_Domsch@dell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.