public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Yuhong Bao <yuhongbao_386@hotmail.com>
Cc: hancockrwd@gmail.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 12:29:12 +0900	[thread overview]
Message-ID: <4B85EE88.5050506@kernel.org> (raw)
In-Reply-To: <SNT125-W36AFF0BF953EABAC9A0432C3400@phx.gbl>

Hello,

On 02/25/2010 12:15 PM, Yuhong Bao wrote:
>> (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. 
> 
> Except that unfortunately, Intel with Lynnfield and Clarkdale decided 
> to do market segmentation on the VT-d feature. 
> This could be done because both have an integrated northbridge.
> With Lynnfield, the very common Core i5 750 CPU do not support VT-d,
> but the Core i7 800 series does.
> With Clarkdale, the very common Core i3 500 series do not support VT-d,
> but the Core i5 600 series does, except the 661.
> Not to mention that in the Core 2 generation, VT-d was available only
> on Q35/Q45/X38/X48 chipsets.

Arghhh.... I hate when intel pulls this type of 'product
differentiation' stunts.  At any rate, I'm doubtful swiotlb'ing for
usb2.0 would be noticeable at all.

Thanks.

-- 
tejun

  reply	other threads:[~2010-02-25  3:19 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
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 [this message]
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=4B85EE88.5050506@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