Joel wrote:
> We may not be able to use the same flag after all due to our need to mark buffer
> pages as user.
Agreed - we have separate flags. I want exactly user address space
pages. You want really easy to reclaim pages. You have good
performance justifications for your choice. I have just "design
purity", so if for some reason there was a dire shortage of GFP bits,
I suspect it is I who should give, not you.
> > +#define __GFP_BITS_SHIFT 21 /* Room for 20 __GFP_FOO bits */
>
> Yep.
Once this is merged with current Linux, which already has GFP_HARDWALL,
I presume you will be back up to 21 bits, code and comment.
As I noted in another message the "USER" and the comment in:
#define __GFP_USER 0x40000u /* User is a userspace user */
are a bit misleading now. Perhaps GFP_EASYRCLM?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |