From: Andrew Morton <akpm@linux-foundation.org>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: Linux-MM <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, Dan Streetman <ddstreet@ieee.org>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH v3] z3fold: use per-page read/write lock
Date: Wed, 9 Nov 2016 14:33:04 -0800 [thread overview]
Message-ID: <20161109143304.538885b06a4b5d2289da1e52@linux-foundation.org> (raw)
In-Reply-To: <20161109115531.81d2a3fd4313236d483510f0@gmail.com>
On Wed, 9 Nov 2016 11:55:31 +0100 Vitaly Wool <vitalywool@gmail.com> wrote:
> Subject: [PATCH v3] z3fold: use per-page read/write lock
I've rewritten the title to "mm/z3fold.c: use per-page spinlock"
(I prefer to have "mm" in the title to easily identify it as an MM
patch, and using "mm: z3fold: ..." seems odd when the actual pathname
conveys the same info.)
>
> Most of z3fold operations are in-page, such as modifying z3fold
> page header or moving z3fold objects within a page. Taking
> per-pool spinlock to protect per-page objects is therefore
> suboptimal, and the idea of having a per-page spinlock (or rwlock)
> has been around for some time. However, adding one directly to the
> z3fold header makes the latter quite big on some systems so that
> it won't fit in a signle chunk.
>
> This patch implements spinlock-based per-page locking mechanism
> which is lightweight enough to fit into the z3fold header.
--
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:[~2016-11-09 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 10:55 Vitaly Wool
2016-11-09 22:33 ` Andrew Morton [this message]
2016-11-09 23:01 ` Andi Kleen
2016-11-09 23:22 ` Thomas Gleixner
2016-11-10 0:32 ` 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=20161109143304.538885b06a4b5d2289da1e52@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=ddstreet@ieee.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vitalywool@gmail.com \
/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