From: Matt Domsch <Matt_Domsch@Dell.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Narendra_K@Dell.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org, Jordan_Hargrave@Dell.com,
Charles_Rose@Dell.com
Subject: Re: [PATCH] Enable pci=bfsort by default on future Dell systems
Date: Tue, 14 Dec 2010 20:51:41 -0600 [thread overview]
Message-ID: <20101215025141.GA32334@auslistsprd01.us.dell.com> (raw)
In-Reply-To: <20101214201242.GC21909@parisc-linux.org>
On Tue, Dec 14, 2010 at 01:12:43PM -0700, Matthew Wilcox wrote:
> Actually, how about we introduce a smaller patch that just makes
> bfsort the default for all machines with a BIOS date of 2011 or later?
> bfsort was what we always intended; it was unintentionally broken for,
> what, five years, and the only reason not to revert it was to not break
> setups that had come to rely on it.
>
> So just make it the default for all future systems, no matter what
> manufacturer.
This approach would hit all systems that install a newly issued BIOS
after 2010, which could cause a change in behaviour for such systems.
I don't know how to get a "system manufactured" date or "system first
powered on" date generically (IIRC these might be exposed in
vendor-specific fields on Dell systems).
I'm not opposed, but it could result in a change of behavior for
still-maintained (as evidenced by newly issued BIOSes) systems.
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO
next prev parent reply other threads:[~2010-12-15 2:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 17:57 [PATCH] Enable pci=bfsort by default on future Dell systems Narendra_K
2010-12-14 19:54 ` Matt Domsch
2010-12-14 20:12 ` Matthew Wilcox
2010-12-15 2:51 ` Matt Domsch [this message]
2010-12-17 16:17 ` Narendra_K
2010-12-17 18:06 ` Jesse Barnes
2010-12-20 6:54 ` Narendra_K
2011-01-07 22:27 ` Jesse Barnes
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=20101215025141.GA32334@auslistsprd01.us.dell.com \
--to=matt_domsch@dell.com \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
/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