From: Robert Hancock <hancockrwd@gmail.com>
To: Brice Goglin <Brice.Goglin@inria.fr>
Cc: Dan Williams <dan.j.williams@intel.com>,
Maciej Sosnowski <maciej.sosnowski@intel.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: how to get a DMA channel near a process?
Date: Tue, 25 Aug 2009 23:18:46 -0600 [thread overview]
Message-ID: <4A94C5B6.3060907@gmail.com> (raw)
In-Reply-To: <4A93E192.9000109@inria.fr>
On 08/25/2009 07:05 AM, Brice Goglin wrote:
> Hello,
>
> I am playing with DMA engine on a Nehalem box with two X58 chipsets
> (Supermicro X8DAH). My understanding is that there are 8 DMA channels on
> each chipset, so 8 channels near each processor. Unfortunately, my BIOS
Don't think that DMA channel is the term you are looking for, maybe PCI
Express lanes? DMA channels are an ancient ISA thing.
> and 2.6.31-rc still wrongly reports the physical location of my devices
> (it claims all PCI devices are near the first processor) but I worked
> around the problem manually.
Presumably incorrect information in the BIOS tables (SLIT or MADT, maybe?)
>
> The offloaded copy performance changes a lot depending on whether the
> process memory is allocated near the DMA device. So first I would like
> to know if DMA channels are allocated near the requesting
> processor/process. Then I guess it's possible to read the cpu mask near
Not sure quite what you are trying to say here. Normally when memory is
allocated for DMA use for a specific device I believe the kernel tries
to allocate it on the same node that the device is attached to.
> a given chan by following chan->dev.device up to the pci device, right?
> But is there any way to request a DMA channel near a specific socket or
> NUMA node or cpu mask?
>
> Thanks,
> Brice
>
>
next prev parent reply other threads:[~2009-08-26 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 13:05 how to get a DMA channel near a process? Brice Goglin
2009-08-26 5:18 ` Robert Hancock [this message]
2009-08-26 5:32 ` Brice Goglin
2009-08-26 6:10 ` Dan Williams
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=4A94C5B6.3060907@gmail.com \
--to=hancockrwd@gmail.com \
--cc=Brice.Goglin@inria.fr \
--cc=dan.j.williams@intel.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