From: Vitaly Wool <vitalywool@gmail.com>
To: Dan Streetman <ddstreet@ieee.org>
Cc: Linux-MM <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATH] z3fold: extend compaction function
Date: Sat, 26 Nov 2016 10:09:27 +0100 [thread overview]
Message-ID: <CAMJBoFMaytBR1JwdbsoZ5Q6DzFd40q81Gfi93kiG302us2qRbQ@mail.gmail.com> (raw)
In-Reply-To: <CALZtONAJLTJikY1Nr0GUa9MPkfWcnaygXKzvy-RwJ_7dp2-sWw@mail.gmail.com>
On Fri, Nov 25, 2016 at 10:17 PM, Dan Streetman <ddstreet@ieee.org> wrote:
> On Fri, Nov 25, 2016 at 9:43 AM, Dan Streetman <ddstreet@ieee.org> wrote:
>> On Thu, Nov 3, 2016 at 5:04 PM, Vitaly Wool <vitalywool@gmail.com> wrote:
>>> z3fold_compact_page() currently only handles the situation when
>>> there's a single middle chunk within the z3fold page. However it
>>> may be worth it to move middle chunk closer to either first or
>>> last chunk, whichever is there, if the gap between them is big
>>> enough.
>>>
>>> This patch adds the relevant code, using BIG_CHUNK_GAP define as
>>> a threshold for middle chunk to be worth moving.
>>>
>>> Signed-off-by: Vitaly Wool <vitalywool@gmail.com>
>>
>> with the bikeshedding comments below, looks good.
>>
>> Acked-by: Dan Streetman <ddstreet@ieee.org>
>>
>>> ---
>>> mm/z3fold.c | 60 +++++++++++++++++++++++++++++++++++++++++++++++-------------
>>> 1 file changed, 47 insertions(+), 13 deletions(-)
>>>
>>> diff --git a/mm/z3fold.c b/mm/z3fold.c
>>> index 4d02280..fea6791 100644
>>> --- a/mm/z3fold.c
>>> +++ b/mm/z3fold.c
>>> @@ -250,26 +250,60 @@ static void z3fold_destroy_pool(struct z3fold_pool *pool)
>>> kfree(pool);
>>> }
>>>
>>> +static inline void *mchunk_memmove(struct z3fold_header *zhdr,
>>> + unsigned short dst_chunk)
>>> +{
>>> + void *beg = zhdr;
>>> + return memmove(beg + (dst_chunk << CHUNK_SHIFT),
>>> + beg + (zhdr->start_middle << CHUNK_SHIFT),
>>> + zhdr->middle_chunks << CHUNK_SHIFT);
>>> +}
>>> +
>>> +#define BIG_CHUNK_GAP 3
>>> /* Has to be called with lock held */
>>> static int z3fold_compact_page(struct z3fold_header *zhdr)
>>> {
>>> struct page *page = virt_to_page(zhdr);
>>> - void *beg = zhdr;
>>> + int ret = 0;
>>> +
>>> + if (test_bit(MIDDLE_CHUNK_MAPPED, &page->private))
>>> + goto out;
>>>
>>> + if (zhdr->middle_chunks != 0) {
>>
>> bikeshed: this check could be moved up also, as if there's no middle
>> chunk there is no compacting to do and we can just return 0. saves a
>> tab in all the code below.
>>
>>> + if (zhdr->first_chunks == 0 && zhdr->last_chunks == 0) {
>>> + mchunk_memmove(zhdr, 1); /* move to the beginning */
>>> + zhdr->first_chunks = zhdr->middle_chunks;
>>> + zhdr->middle_chunks = 0;
>>> + zhdr->start_middle = 0;
>>> + zhdr->first_num++;
>>> + ret = 1;
>>> + goto out;
>>> + }
>>>
>>> - if (!test_bit(MIDDLE_CHUNK_MAPPED, &page->private) &&
>>> - zhdr->middle_chunks != 0 &&
>>> - zhdr->first_chunks == 0 && zhdr->last_chunks == 0) {
>>> - memmove(beg + ZHDR_SIZE_ALIGNED,
>>> - beg + (zhdr->start_middle << CHUNK_SHIFT),
>>> - zhdr->middle_chunks << CHUNK_SHIFT);
>>> - zhdr->first_chunks = zhdr->middle_chunks;
>>> - zhdr->middle_chunks = 0;
>>> - zhdr->start_middle = 0;
>>> - zhdr->first_num++;
>>> - return 1;
>>> + /*
>>> + * moving data is expensive, so let's only do that if
>>> + * there's substantial gain (at least BIG_CHUNK_GAP chunks)
>>> + */
>>> + if (zhdr->first_chunks != 0 && zhdr->last_chunks == 0 &&
>>> + zhdr->start_middle > zhdr->first_chunks + BIG_CHUNK_GAP) {
>>> + mchunk_memmove(zhdr, zhdr->first_chunks + 1);
>>> + zhdr->start_middle = zhdr->first_chunks + 1;
>>> + ret = 1;
>>> + goto out;
>>> + }
>>> + if (zhdr->last_chunks != 0 && zhdr->first_chunks == 0 &&
>>> + zhdr->middle_chunks + zhdr->last_chunks <=
>>> + NCHUNKS - zhdr->start_middle - BIG_CHUNK_GAP) {
>>> + unsigned short new_start = NCHUNKS - zhdr->last_chunks -
>>> + zhdr->middle_chunks;
>
> after closer review, I see that this is wrong. NCHUNKS isn't the
> total number of page chunks, it's the total number of chunks minus the
> header chunk(s). so that calculation of where the new start is, is
> wrong. it should use the total page chunks, not the NCHUNKS, because
> start_middle already accounts for the header chunk(s). Probably a new
> macro would help.
>
> Also, the num_free_chunks() function makes the same mistake:
>
> int nfree_after = zhdr->last_chunks ?
> 0 : NCHUNKS - zhdr->start_middle - zhdr->middle_chunks;
>
> that's wrong, it should be something like:
>
> #define TOTAL_CHUNKS (PAGE_SIZE >> CHUNK_SHIFT)
> ...
> int nfree_after = zhdr->last_chunks ?
> 0 : TOTAL_CHUNKS - zhdr->start_middle - zhdr->middle_chunks;
Right, will fix.
~vitaly
--
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>
prev parent reply other threads:[~2016-11-26 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 21:04 Vitaly Wool
2016-11-03 21:16 ` Andrew Morton
2016-11-03 21:35 ` Vitaly Wool
2016-11-25 14:43 ` Dan Streetman
2016-11-25 21:17 ` Dan Streetman
2016-11-26 9:09 ` Vitaly Wool [this message]
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=CAMJBoFMaytBR1JwdbsoZ5Q6DzFd40q81Gfi93kiG302us2qRbQ@mail.gmail.com \
--to=vitalywool@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox