The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Phillip Susi <psusi@cfl.rr.com>, Jun Sun <jsun@junsun.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Can Linux live without DMA zone?
Date: Fri, 03 Nov 2006 18:54:13 +0100	[thread overview]
Message-ID: <m364dwju0q.fsf@defiant.localdomain> (raw)
In-Reply-To: <1162505945.14530.98.camel@laptopd505.fenrus.org> (Arjan van de Ven's message of "Thu, 02 Nov 2006 23:19:05 +0100")

Arjan van de Ven <arjan@infradead.org> writes:

> you're right in theory, but the kernel only has a few pools of memory
> available, but not at every bit boundary. there is a 32 bit pool
> (GFP_DMA32) on some, a 30-ish bit pool (GFP_KERNEL) on others, and a 24
> bit pool (GFP_DMA) with basically nothing inbetween.

Perhaps naive question, but... what's wrong with allocating memory
from the top (within given address mask[1], size-wise)? I think we
don't allocate more than 1 page with kmalloc anymore, do we?

[1] - some devices (a specific StrongARM only?) need non-continuous
masks due to a hardware bug(s).
-- 
Krzysztof Halasa

  parent reply	other threads:[~2006-11-03 17:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02  2:15 Can Linux live without DMA zone? Jun Sun
2006-11-02  9:16 ` Arjan van de Ven
2006-11-02 10:32 ` Paul Mundt
2006-11-02 16:32 ` Phillip Susi
2006-11-02 16:57   ` Arjan van de Ven
2006-11-02 19:08     ` Phillip Susi
2006-11-02 20:10       ` Arjan van de Ven
2006-11-02 21:26         ` Phillip Susi
2006-11-02 22:19           ` Arjan van de Ven
2006-11-02 23:17             ` Jun Sun
2006-11-02 23:24               ` Stephen Hemminger
2006-11-06  2:19               ` Phillip Susi
2006-11-03 17:54             ` Krzysztof Halasa [this message]
2006-11-02 18:02   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2006-11-02  3:43 Conke Hu
2006-11-02  7:13 ` Peter Zijlstra
2006-11-02 16:13   ` Christoph Lameter
2006-11-02 10:33 Conke Hu
2006-11-02 10:51 ` Arjan van de Ven
2006-11-02 13:09 ` Alan Cox

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=m364dwju0q.fsf@defiant.localdomain \
    --to=khc@pm.waw.pl \
    --cc=arjan@infradead.org \
    --cc=jsun@junsun.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=psusi@cfl.rr.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