From: Andrew Morton <akpm@linux-foundation.org>
To: Igor Stoppa <igor.stoppa@gmail.com>
Cc: willy@infradead.org, mhocko@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, igor.stoppa@huawei.com
Subject: Re: [PATCH 0/2] mm: tweaks for improving use of vmap_area
Date: Mon, 30 Apr 2018 16:15:15 -0700 [thread overview]
Message-ID: <20180430161515.118e6538e4d4f1cc4ae425cc@linux-foundation.org> (raw)
In-Reply-To: <20180426234243.22267-1-igor.stoppa@huawei.com>
On Fri, 27 Apr 2018 03:42:41 +0400 Igor Stoppa <igor.stoppa@gmail.com> wrote:
> These two patches were written in preparation for the creation of
> protectable memory, however their use is not limited to pmalloc and can
> improve the use of virtally contigous memory.
>
> The first provides a faster path from struct page to the vm_struct that
> tracks it.
>
> The second patch renames a single linked list field inside of vmap_area.
> The list is currently used only for disposing of the data structure, once
> it is not in use anymore.
> Which means that it cold be used for other purposes while it'not queued
> for destruction.
The patches look benign to me (feel free to add my ack), but I'm not
seeing a reason to apply them at this time?
next prev parent reply other threads:[~2018-04-30 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 23:42 Igor Stoppa
2018-04-26 23:42 ` [PATCH 1/2] struct page: add field for vm_struct Igor Stoppa
2018-04-26 23:42 ` [PATCH 2/2] vmalloc: rename llist field in vmap_area Igor Stoppa
2018-04-30 23:15 ` Andrew Morton [this message]
2018-05-02 0:05 ` [PATCH 0/2] mm: tweaks for improving use of vmap_area 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=20180430161515.118e6538e4d4f1cc4ae425cc@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=igor.stoppa@gmail.com \
--cc=igor.stoppa@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=willy@infradead.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