From: Nitin Gupta <ngupta@vflare.org>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
Christoph Hellwig <hch@infradead.org>,
Jens Axboe <jens.axboe@oracle.com>,
Andi Kleen <andi@firstfloor.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [mmotm] comment on swap notify locking constraints
Date: Thu, 14 Jan 2010 23:29:47 +0530 [thread overview]
Message-ID: <4B4F5B93.8030202@vflare.org> (raw)
In-Reply-To: <alpine.LSU.2.00.1001141503140.1943@sister.anvils>
On 01/14/2010 08:40 PM, Hugh Dickins wrote:
> On Thu, 14 Jan 2010, Nitin Gupta wrote:
>
>> A block device makes swap_slot_free_notify() callback
>> when the last reference to a swap slot is dropped.
>>
>> This callback is made under swap_lock and often with
>> lock for corresponding swapcache page also held. This
>> is a note of warning for registered callback function
>> which must meet these constraints.
>
> You're right that the page lock of the corresponding swapcache page
> may be held there, but that isn't what worried me enough to ask for
> a comment: it's the page table lock (sometimes we call it pte lock),
> a spinlock like the swap_lock, being held there that particularly
> deserves comment. We don't want someone going to lots of effort
> to avoid holding swap_lock there, only to find that effort wasted
> because page table lock is also held.
Thanks for the review.
I was missing this important point regarding pte lock. I will edit
the comment and resend the patch.
Nitin
>>
>> Signed-off-by: Nitin Gupta <ngupta@vflare.org>
>> ---
>> include/linux/blkdev.h | 1 +
>> 1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
>> index 14b95a3..e3dcff6 100644
>> --- a/include/linux/blkdev.h
>> +++ b/include/linux/blkdev.h
>> @@ -1295,6 +1295,7 @@ struct block_device_operations {
>> unsigned long long);
>> int (*revalidate_disk) (struct gendisk *);
>> int (*getgeo)(struct block_device *, struct hd_geometry *);
>> + /* this callback is with swap_lock and often page lock also held */
>
> and page table lock
>
>> void (*swap_slot_free_notify) (struct block_device *, unsigned long);
>> struct module *owner;
>> };
>> --
>> 1.6.2.5
>
prev parent reply other threads:[~2010-01-14 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 14:32 [PATCH] [mmotm] comment on swap notify locking constraints Nitin Gupta
2010-01-14 15:10 ` Hugh Dickins
2010-01-14 17:59 ` Nitin Gupta [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=4B4F5B93.8030202@vflare.org \
--to=ngupta@vflare.org \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hch@infradead.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=viro@ZenIV.linux.org.uk \
/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