The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Dave Airlie <airlied@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org
Subject: Re: drm + 4GB RAM + swiotlb = drm craps out
Date: Mon, 2 Apr 2007 08:40:46 +0200	[thread overview]
Message-ID: <20070402064046.GA24269@one.firstfloor.org> (raw)
In-Reply-To: <21d7e9970704012238x2c5e6c62hc30933d9575910cf@mail.gmail.com>

On Mon, Apr 02, 2007 at 03:38:48PM +1000, Dave Airlie wrote:
> Doesn't __get_free_pages give me physically linear memory, which while
> nice it isn't essential for what I need, so if I can't get my full
> allocation I could in theory just start to fallback down the orders
> and calling it multiple times to actually get the amount of memory I

You get linear memory. Just get individual pages.

If you want to merge them you can use vmap(),
but in the kernel you should probably just fix your in kernel 
code to not require that and work with sg lists.

If you get the pages piece by piece you can also more easily
remap them linearly into user space.

> need, this just seems overly cumbersome when what I really want is
> vmalloc_32 to just work correctly on 64-bit systems... (why doesn't
> vmalloc_32 pass __GFP_DMA32 to the allocator????)

It probably should, but see second part of sentence above.

And please never put closed lists in cc of l-k posts. Evil cc dropped.

-Andi


  reply	other threads:[~2007-04-02  6:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 23:44 drm + 4GB RAM + swiotlb = drm craps out Dave Airlie
2007-04-02  3:11 ` David Miller
2007-04-02  4:08   ` Dave Airlie
2007-04-02  5:08     ` David Miller
2007-04-02  5:15       ` Dave Airlie
2007-04-02  5:24         ` David Miller
2007-04-02  6:27         ` Andi Kleen
2007-04-02  5:38           ` Dave Airlie
2007-04-02  6:40             ` Andi Kleen [this message]
2007-04-02  6:52               ` Dave Airlie
2007-04-02  6:55                 ` Andi Kleen

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=20070402064046.GA24269@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=airlied@gmail.com \
    --cc=davem@davemloft.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