From: Phillip Susi <psusi@cfl.rr.com>
To: Jun Sun <jsun@junsun.net>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: Can Linux live without DMA zone?
Date: Sun, 05 Nov 2006 21:19:24 -0500 [thread overview]
Message-ID: <454E9BAC.1000009@cfl.rr.com> (raw)
In-Reply-To: <20061102231715.GA10902@srv.junsun.net>
Jun Sun wrote:
> Perhaps a better solution is to
>
> 1. get rid of DMA zone
>
> 2. have another alloc funciton (e.g., kmalloc_range()) which takes an
> extra pair of parameters to indicate the desired range for the
> allocated memory. Most DMA buffers are allocated during start-up.
> So the alloc operations should generally be successful.
>
> 3. convert drivers over to use the new function.
>
> Cheers.
>
> Jun
> are allocated at start-up time.
That is what I was thinking. You don't need lots of separate pools, you
just need the standard allocator to prefer higher addresses, and then
the bounce routines need to simply check if the existing user buffer
happens to already be within the area the hardware can address ( which
it often will be ), and if not, copy the data to pages allocated in
lower memory.
next prev parent reply other threads:[~2006-11-06 2:19 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 [this message]
2006-11-03 17:54 ` Krzysztof Halasa
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=454E9BAC.1000009@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=arjan@infradead.org \
--cc=jsun@junsun.net \
--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