public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "MEHTA,HIREN (A-SanJose,ex1)" <hiren_mehta@agilent.com>
Cc: "'Ralf Baechle'" <ralf@uni-koblenz.de>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: pci_alloc_consistent question
Date: Fri, 19 Oct 2001 17:37:45 -0400	[thread overview]
Message-ID: <3BD09D29.2ACF840E@mandrakesoft.com> (raw)
In-Reply-To: <01A7DAF31F93D511AEE300D0B706ED9208E4A5@axcs13.cos.agilent.com>

"MEHTA,HIREN (A-SanJose,ex1)" wrote:
> so, what is the conservative number ? 1MB ?

FWIW, if you need more than 1-4MB, you can use alloc_bootmem at system
boot to reserve huge amounts of contiguous memory...  (not that anything
but lame hardware requires that anymore)

> -----Original Message-----
> On Fri, Oct 19, 2001 at 12:32:19PM -0600, MEHTA,HIREN (A-SanJose,ex1) wrote:
> 
> > Is there any limitation on the amount of contiguous dmaable memory that
> > can be allocated using a single call to pci_alloc_consistent() ?
> 
> Entirely platform dependant.  On some systems the total available DMA memory
> for DMA may be as limited as 1mb, others have limits like 16mb yet other can
> support the entire 32-bit address space for DMA.  So in case of doubt be
> conservative.

-- 
Jeff Garzik      | Only so many songs can be sung
Building 1024    | with two lips, two lungs, and one tongue.
MandrakeSoft     |         - nomeansno

  reply	other threads:[~2001-10-19 21:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-19 21:24 pci_alloc_consistent question MEHTA,HIREN (A-SanJose,ex1)
2001-10-19 21:37 ` Jeff Garzik [this message]
2001-10-19 21:59 ` Ralf Baechle
  -- strict thread matches above, loose matches on Subject: below --
2001-10-19 18:32 MEHTA,HIREN (A-SanJose,ex1)
2001-10-19 18:51 ` Francois Romieu
2001-10-19 20:57 ` Ralf Baechle

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=3BD09D29.2ACF840E@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=hiren_mehta@agilent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ralf@uni-koblenz.de \
    /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