From: Jiang Liu <jiang.liu@huawei.com>
To: "Sosnowski, Maciej" <maciej.sosnowski@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Keping Chen <chenkeping@huawei.com>
Subject: Re: [RESEND,PATCH] DCA, x86: fix invalid memory access in DCA core
Date: Thu, 24 May 2012 09:24:48 +0800 [thread overview]
Message-ID: <4FBD8DE0.7070800@huawei.com> (raw)
In-Reply-To: <436EC33EF05C3442BBF5497FC9483FF416274D2A@IRSMSX101.ger.corp.intel.com>
Hi Maciej,
Thanks for your help. Could you also help to review the IOAT
hotplug patch at http://www.spinics.net/lists/linux-pci/msg15287.html?
It's to support Intel IOAT device hotplug.
Thanks!
On 2012-5-23 23:11, Sosnowski, Maciej wrote:
> On Fri, May 18, 2012 4:31 PM, Jiang Liu<liuj97@gmail.com> wrote:
>>
>> On 05/18/2012 10:10 PM, Sosnowski, Maciej wrote:
>>> On Thu, May 07, May 10, 2012 3:59 AM, Jiang Liu<liuj97@gmail.com> wrote:
>>>>
>>>> Hi Maciej,
>>>> I feel we may also need to tune the multiple IOH support in DCA.
>>>> Multiple IOH support is disabled for CB3.0 devices, how about CB3.1
>> devices
>>>> in Ivrbridge or SandyBridge? Does the hardware limitation still exist? Or
>>>> could we support multiple IOHs with IvyBridge and SandyBridge?
>>>> If multiple IOH is supported, I think we should move the logic to
>>>> disable multiple IOH support for CB3.0 from DCA core into ioatdma. I have
>>>> also prepared two patches for that two.
>>>> Thanks!
>>>>
>>>
>>> At this point I do not think we would need to tune multiple IOH for DCA.
>>> The limitation you mention applies only to CB3.0. I do not think DCA is
>> supported
>>> with Sandy Bridge / Ivy Bridge regardless of multi-IOH case but let me
>> confirm it
>>> yet.
>> It seems that Intel introduces DDIO technology for IvyBridge. Does it replace
>> DCA
>> technology on new platforms?
>> Thanks!
>
> Yes, in general DDIO is used instead of DCA on new platforms.
> Note however that DDIO is supported in Xeon E5 only, not in Xeon E3.
>
> Thanks,
> Maciej
>
>
next prev parent reply other threads:[~2012-05-24 1:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 15:58 [RESEND,PATCH] DCA, x86: fix invalid memory access in DCA core Jiang Liu
2012-05-09 15:24 ` Sosnowski, Maciej
2012-05-10 1:59 ` Jiang Liu
2012-05-18 14:10 ` Sosnowski, Maciej
2012-05-18 14:30 ` Jiang Liu
2012-05-23 15:11 ` Sosnowski, Maciej
2012-05-24 1:24 ` Jiang Liu [this message]
2012-05-18 14:04 ` Sosnowski, Maciej
2012-05-18 14:49 ` Jiang Liu
2012-05-21 12:27 ` Jiang Liu
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=4FBD8DE0.7070800@huawei.com \
--to=jiang.liu@huawei.com \
--cc=chenkeping@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@intel.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