From: Terrence Martin <tmartin@physics.ucsd.edu>
To: linux-kernel@vger.kernel.org
Subject: Bigphysarea patch and 2.6, advice requested
Date: Fri, 02 Apr 2004 14:42:49 -0800 [thread overview]
Message-ID: <406DEC69.6010909@physics.ucsd.edu> (raw)
Hi,
I have been asked to investigate the 2.6 kernel for a high performance
computing application. One of the questions we have is whether or not
2.6 supports the so called "bigphysarea" patch, or "hack" as it is
sometimes referred to or has some built in mechanism to accomplish the
same ends, large contiguous blocks of memory suitable for DMA.
The problem is that the project would like to use large contiguous areas
of memory for the purposes of DMA for various custom made PCI cards. I
have read in a couple of posts that when the PCI device supports
scatter/gather that is the preferred mechanism. The issue is that there
is a very good chance that not all of the devices have the
scatter/gather mechanism implemented on board.
Is there anything in 2.6 that accomplishes the same ends as the 2.4
based bigphysarea patch/hack? What are other people doing when they
need this functionality and also want to run 2.6?
Thanks for any insight you can provide.
Terrence Martin
UCSD Physics
reply other threads:[~2004-04-02 22:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=406DEC69.6010909@physics.ucsd.edu \
--to=tmartin@physics.ucsd.edu \
--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