From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Holger Kiehl <Holger.Kiehl@dwd.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Question regarding CONFIG_DMA_ENGINE
Date: Mon, 25 Sep 2006 18:56:48 -0400 [thread overview]
Message-ID: <45185EB0.90300@ens-lyon.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0609211249160.9397@diagnostix.dwd.de>
Holger Kiehl wrote:
> Hello
>
> Is setting this option and CONFIG_NET_DMA usefull even when you do not
> have
> the hardware?
>
> And what hardware is required for this? Is this DMA engine located on
> the network or raid card, or is this something in the chipset? Which
> chipset or cards do have such an engine?
>
> Thanks,
> Holger
I guess the option is completely useless without such hardware.
For now, you need a Intel E5000 chipset (Blackford and co.). It exports
a special PCI device (id 8086:1a38) for DMA. No other device is
supported so far, but some Raid stuff have been proposed recently IIRC.
Brice
prev parent reply other threads:[~2006-09-25 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 13:33 Question regarding CONFIG_DMA_ENGINE Holger Kiehl
2006-09-25 22:56 ` Brice Goglin [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=45185EB0.90300@ens-lyon.org \
--to=brice.goglin@ens-lyon.org \
--cc=Holger.Kiehl@dwd.de \
--cc=linux-kernel@vger.kernel.org \
/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