linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Ralf Baechle <ralf@linux-mips.org>,
	x86@kernel.org
Subject: Re: [RFC 1/1] bootmem: move big allocations behing 4G
Date: Wed, 20 Jan 2010 14:50:13 +0100	[thread overview]
Message-ID: <4B570A15.8040601@gmail.com> (raw)
In-Reply-To: <20100119143355.GB7932@cmpxchg.org>

On 01/19/2010 03:33 PM, Johannes Weiner wrote:
> --- a/include/linux/bootmem.h
> +++ b/include/linux/bootmem.h
> @@ -96,20 +96,26 @@ extern void *__alloc_bootmem_low_node(pg_data_t *pgdat,
>  				      unsigned long align,
>  				      unsigned long goal);
>  
> +#ifdef MAX_DMA32_PFN
> +#define BOOTMEM_DEFAULT_GOAL	(__pa(MAX_DMA32_PFN << PAGE_SHIFT))
> +#else
> +#define BOOTMEM_DEFAULT_GOAL	MAX_DMA_ADDRESS

I just noticed this should write:
#define BOOTMEM_DEFAULT_GOAL   __pa(MAX_DMA_ADDRESS)

> +#endif
> +
>  #define alloc_bootmem(x) \
> -	__alloc_bootmem(x, SMP_CACHE_BYTES, __pa(MAX_DMA_ADDRESS))
> +	__alloc_bootmem(x, SMP_CACHE_BYTES, BOOTMEM_DEFAULT_GOAL)


-- 
js

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2010-01-20 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 22:56 [RFC 1/1] bootmem: move big allocations behing 4G Jiri Slaby
2010-01-19 14:33 ` Johannes Weiner
2010-01-19 22:02   ` Jiri Slaby
2010-01-20 13:50   ` Jiri Slaby [this message]
2010-01-20 15:30     ` Johannes Weiner
2010-01-20 22:53       ` [PATCH] bootmem: avoid DMA32 zone by default Johannes Weiner
2010-01-20 23:12         ` Jiri Slaby

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=4B570A15.8040601@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ralf@linux-mips.org \
    --cc=x86@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;
as well as URLs for NNTP newsgroup(s).