From: "Christophe Beaumont" <christophe@paracel.com>
To: <root@chaos.analogic.com>
Cc: "kernel Linux" <linux-kernel@vger.kernel.org>
Subject: RE: DMA memory limitation?
Date: Thu, 5 Jul 2001 10:07:17 -0700 [thread overview]
Message-ID: <NFBBINOGHMOOBMPNBAHKCEPECEAA.christophe@paracel.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1010705082119.19376B-100000@chaos.analogic.com>
> On Thu, 5 Jul 2001, Vasu Varma P V wrote:
>
> > Hi,
> >
> > Is there any limitation on DMA memory we can allocate using
> > kmalloc(size, GFP_DMA)? I am not able to acquire more than
> > 14MB of the mem using this on my PCI SMP box with 256MB ram.
> > I think there is restriction on ISA boards of 16MB.
> > Can we increase it ?
> >
> > thx,
> > Vasu
>
> 14MB of DMA(able) memory? Err. I think you are trying to
> do something you would never need to do.
>
And what is that supposed to be????
I have a piece of pretty well designed hardware here... and my
application requires me to have the PCI board to random access
in master mode a whole lot of memory (anywhere from 128MEGS to
1GIG... and possibly more...) so I really do need BIG DMA buffers
(I don't say huge anymore as one can get 1/2 Gig of RAM for just
over 120 bucks???)...
There is no way I can have the piece of hardware behave in
another fashion... and NO it is NOT broken (when you do BOTH
hardware & software, you know about BOTH limitations... there
are just some cases where you have to face some unique issues).
the mem=1024M works pretty fine once you have figured out how
to handle in a fairly simple way this "reserved" memory...
So please software people... do not blame it all on the
hardware... =)
Chris.
next prev parent reply other threads:[~2001-07-05 17:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 11:47 Vasu Varma P V
2001-07-05 11:53 ` Alan Cox
2001-07-05 11:54 ` Arjan van de Ven
2001-07-05 12:37 ` Vasu Varma P V
2001-07-05 12:37 ` Richard B. Johnson
2001-07-05 17:07 ` Christophe Beaumont [this message]
2001-07-05 17:19 ` Richard B. Johnson
2001-07-06 8:59 ` Helge Hafting
2001-07-06 9:44 ` Steffen Persvold
2001-07-06 11:08 ` Alan Cox
2001-07-06 11:27 ` Jeff Garzik
2001-07-06 15:16 ` Steffen Persvold
2001-07-06 15:39 ` Jeff Garzik
2001-07-06 15:48 ` Alan Cox
2001-07-06 15:56 Matt_Domsch
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=NFBBINOGHMOOBMPNBAHKCEPECEAA.christophe@paracel.com \
--to=christophe@paracel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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®