From: Igor Stoppa <igor.stoppa@huawei.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: namhyung@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Remove hardcoding of ___GFP_xxx bitmasks
Date: Fri, 28 Apr 2017 10:43:09 +0300 [thread overview]
Message-ID: <4b077316-b381-08d7-7797-1eaf65d01a02@huawei.com> (raw)
In-Reply-To: <20170428074028.GF8143@dhcp22.suse.cz>
On 28/04/17 10:40, Michal Hocko wrote:
> Do not add a new zone, really. What you seem to be looking for is an
> allocator on top of the page/memblock allocator which does write
> protection on top. I understand that you would like to avoid object
> management duplication but I am not really sure how much you can re-use
> what slab allocators do already, anyway. I will respond to the original
> thread to not mix things together.
I'm writing an alternative different proposal, let's call it last attempt.
Should be ready in a few minutes.
thanks, igor
--
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:[~2017-04-28 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 13:35 [PATCH 0/1] mm: Improve consistency of ___GFP_xxx masks Igor Stoppa
2017-04-26 13:35 ` [PATCH 1/1] Remove hardcoding of ___GFP_xxx bitmasks Igor Stoppa
2017-04-26 14:47 ` Michal Hocko
2017-04-26 15:29 ` Igor Stoppa
2017-04-27 12:16 ` Question on ___GFP_NOLOCKDEP - Was: " Igor Stoppa
2017-04-27 13:35 ` Michal Hocko
2017-05-10 15:24 ` Vlastimil Babka
2017-04-27 12:18 ` Igor Stoppa
2017-04-27 13:41 ` Michal Hocko
2017-04-27 14:06 ` Igor Stoppa
2017-04-28 7:40 ` Michal Hocko
2017-04-28 7:43 ` Igor Stoppa [this message]
2017-04-28 8:13 ` Igor Stoppa
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=4b077316-b381-08d7-7797-1eaf65d01a02@huawei.com \
--to=igor.stoppa@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=namhyung@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