mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Brice Goglin <Brice.Goglin@inria.fr>
Cc: 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:10:09 -0700	[thread overview]
Message-ID: <e9c3a7c20908252310n72bc3375nf79912bac40c0d92@mail.gmail.com> (raw)
In-Reply-To: <4A93E192.9000109@inria.fr>

On Tue, Aug 25, 2009 at 6:05 AM, Brice Goglin<Brice.Goglin@inria.fr> 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
> 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.
>
> 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
> 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?

If we can determine the topology of which chipset is closer to which
cpu package then we can modify the dmaengine channel_table to return
"local" channels via dma_find_channel().  The current allocation
policy is blind per-cpu round robin such that cpu-0 gets channel-0,
cpu-1 gets channel-1...  As you pointed out the challenge will be
finding a reliable source for the topology information.

--
Dan

      parent reply	other threads:[~2009-08-26  6:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 13:05 Brice Goglin
2009-08-26  5:18 ` Robert Hancock
2009-08-26  5:32   ` Brice Goglin
2009-08-26  6:10 ` Dan Williams [this message]

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=e9c3a7c20908252310n72bc3375nf79912bac40c0d92@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=Brice.Goglin@inria.fr \
    --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

all inboxes | Powered by JetHome®