From: Andrew Morton <akpm@osdl.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zone gfp_flags generate from ZONE_ constants
Date: Tue, 17 Jan 2006 13:22:14 -0800 [thread overview]
Message-ID: <20060117132214.2db664e2.akpm@osdl.org> (raw)
In-Reply-To: <20060117155227.GA16176@shadowen.org>
Andy Whitcroft <apw@shadowen.org> wrote:
>
> +/*
> + * Generate the zone modifier bit. Zone ZONE_DEFAULT doesn't require a bit
> + * as the absence of all zone modifiers implies this zone. Renormalise the
> + * zone number such that ZONE_DEFAULT is at the bottom and discard it.
> + * These must fit within the bitmask GFP_ZONEMASK defined in linux/mmzone.h.
> + */
> +#define __ZONE_BIT(x) (((x) ^ ZONE_DEFAULT) - 1)
> +#define ZONE_MODIFIER(x) ((__force gfp_t)(((x) == ZONE_DEFAULT)? (0) : \
> + 1UL << __ZONE_BIT(x)))
> +
> +#define __GFP_DMA ZONE_MODIFIER(ZONE_DMA)
> +#define __GFP_HIGHMEM ZONE_MODIFIER(ZONE_HIGHMEM)
> #ifdef CONFIG_DMA_IS_DMA32
> -#define __GFP_DMA32 ((__force gfp_t)0x01) /* ZONE_DMA is ZONE_DMA32 */
> +#define __GFP_DMA32 ZONE_MODIFIER(ZONE_DMA) /* ZONE_DMA is ZONE_DMA32 */
> #elif BITS_PER_LONG < 64
> -#define __GFP_DMA32 ((__force gfp_t)0x00) /* ZONE_NORMAL is ZONE_DMA32 */
> +#define __GFP_DMA32 ZONE_MODIFIER(ZONE_NORMAL) /* ZONE_NORMAL is ZONE_DMA32 */
> #else
> -#define __GFP_DMA32 ((__force gfp_t)0x04) /* Has own ZONE_DMA32 */
> +#define __GFP_DMA32 ZONE_MODIFIER(ZONE_DMA32) /* Has own ZONE_DMA32 */
> #endif
eek. We often look at the hex value of gfp flags in debug output to work
out what sort of allocation is being attempted.
I guess we could print out the values of these things at boot time..
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@osdl.org>
To: Andy Whitcroft <apw@shadowen.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] zone gfp_flags generate from ZONE_ constants
Date: Tue, 17 Jan 2006 13:22:14 -0800 [thread overview]
Message-ID: <20060117132214.2db664e2.akpm@osdl.org> (raw)
In-Reply-To: <20060117155227.GA16176@shadowen.org>
Andy Whitcroft <apw@shadowen.org> wrote:
>
> +/*
> + * Generate the zone modifier bit. Zone ZONE_DEFAULT doesn't require a bit
> + * as the absence of all zone modifiers implies this zone. Renormalise the
> + * zone number such that ZONE_DEFAULT is at the bottom and discard it.
> + * These must fit within the bitmask GFP_ZONEMASK defined in linux/mmzone.h.
> + */
> +#define __ZONE_BIT(x) (((x) ^ ZONE_DEFAULT) - 1)
> +#define ZONE_MODIFIER(x) ((__force gfp_t)(((x) == ZONE_DEFAULT)? (0) : \
> + 1UL << __ZONE_BIT(x)))
> +
> +#define __GFP_DMA ZONE_MODIFIER(ZONE_DMA)
> +#define __GFP_HIGHMEM ZONE_MODIFIER(ZONE_HIGHMEM)
> #ifdef CONFIG_DMA_IS_DMA32
> -#define __GFP_DMA32 ((__force gfp_t)0x01) /* ZONE_DMA is ZONE_DMA32 */
> +#define __GFP_DMA32 ZONE_MODIFIER(ZONE_DMA) /* ZONE_DMA is ZONE_DMA32 */
> #elif BITS_PER_LONG < 64
> -#define __GFP_DMA32 ((__force gfp_t)0x00) /* ZONE_NORMAL is ZONE_DMA32 */
> +#define __GFP_DMA32 ZONE_MODIFIER(ZONE_NORMAL) /* ZONE_NORMAL is ZONE_DMA32 */
> #else
> -#define __GFP_DMA32 ((__force gfp_t)0x04) /* Has own ZONE_DMA32 */
> +#define __GFP_DMA32 ZONE_MODIFIER(ZONE_DMA32) /* Has own ZONE_DMA32 */
> #endif
eek. We often look at the hex value of gfp flags in debug output to work
out what sort of allocation is being attempted.
I guess we could print out the values of these things at boot time..
--
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>
next prev parent reply other threads:[~2006-01-17 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 15:52 [PATCH] zone gfp_flags generate from ZONE_ constants Andy Whitcroft
2006-01-17 15:52 ` Andy Whitcroft
2006-01-17 21:22 ` Andrew Morton [this message]
2006-01-17 21:22 ` Andrew Morton
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=20060117132214.2db664e2.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.