From: Tejun Heo <tj@kernel.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Yuhong Bao <yuhongbao_386@hotmail.com>,
david-b@pacbell.net, greg@kroah.com,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH 2.6.34] ehci-hcd: add option to enable 64-bit DMA support
Date: Thu, 25 Feb 2010 11:28:08 +0900 [thread overview]
Message-ID: <4B85E038.20905@kernel.org> (raw)
In-Reply-To: <51f3faa71002231626q1eb62adeo660c282418f0e01@mail.gmail.com>
Hello,
On 02/24/2010 09:26 AM, Robert Hancock wrote:
> The fact that Windows 7 is now using the feature also means that there
> aren't likely to be too many machines where the 64-bit addressing is
> reported but doesn't work. Which means that aside from the NVIDIA
> quirk, I think enabling 64-bit addressing should be relatively safe.
(following thread from the ATA side) I'm with Greg on this. USB2.0 is
quite slow on today's standard and most 64bit machines now have IOMMU
of some kind anyway. If we have problems on IOMMU (sw or hw)
allocation, I think it should be fixed there.
64bit support even in libata was quite painful with quirky BIOSen, PCI
host controllers, bridges and the controllers themselves. ATA being a
major secondary storage subsystem, libata had to do it but even then
for many those enabling trials, I think we've lost more than we
gained. There just isn't much point in trying to enable a shiny new
feature on an aging platform or technology. The gain might be there
but the downside is we end up catching fallout cases where boot fails
or data corrupts after many months later if we're very lucky. It's
just not worth it.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-02-25 2:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-18 3:10 [PATCH 2.6.34] ehci-hcd: add option to enable 64-bit DMA support Robert Hancock
2010-02-18 4:26 ` Greg KH
2010-02-18 5:13 ` Robert Hancock
2010-02-18 5:22 ` Greg KH
2010-02-19 0:33 ` Robert Hancock
2010-02-19 0:47 ` Greg KH
2010-02-19 3:46 ` Robert Hancock
2010-02-19 3:54 ` Greg KH
2010-02-20 1:30 ` Robert Hancock
2010-02-20 4:26 ` Greg KH
2010-02-20 5:39 ` David Brownell
2010-02-20 7:15 ` Robert Hancock
2010-02-20 8:07 ` David Brownell
2010-02-20 18:13 ` Robert Hancock
2010-02-23 6:48 ` Yuhong Bao
2010-02-24 0:26 ` Robert Hancock
2010-02-25 2:28 ` Tejun Heo [this message]
2010-02-25 2:41 ` Yuhong Bao
2010-02-25 2:58 ` Tejun Heo
2010-02-25 3:15 ` Yuhong Bao
2010-02-25 3:29 ` Tejun Heo
2010-02-25 4:03 ` Oliver Neukum
2010-02-25 5:25 ` Tejun Heo
2010-02-25 16:14 ` Greg KH
2010-02-25 23:15 ` Robert Hancock
2010-02-25 23:25 ` Greg KH
2010-02-26 7:01 ` Oliver Neukum
2010-02-24 3:53 ` SB600 64-bit DMA BIOS misconfiguration (formerly RE: [PATCH 2.6.34] ehci-hcd: add option to enable 64-bit DMA support) Yuhong Bao
2010-02-24 4:30 ` Robert Hancock
2010-02-24 4:33 ` Yuhong Bao
2010-02-24 13:30 ` Huang, Shane
2010-02-23 6:28 ` [PATCH 2.6.34] ehci-hcd: add option to enable 64-bit DMA support Yuhong Bao
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=4B85E038.20905@kernel.org \
--to=tj@kernel.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=yuhongbao_386@hotmail.com \
/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