[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d3a4b4f-22be-9ee9-534b-3ecd97c0b53a@huawei.com>
Date: Thu, 22 Nov 2018 19:22:34 +0800
From: Gao Xiang <gaoxiang25@...wei.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
CC: <devel@...verdev.osuosl.org>, <linux-erofs@...ts.ozlabs.org>,
Chao Yu <yuchao0@...wei.com>,
LKML <linux-kernel@...r.kernel.org>, <weidu.du@...wei.com>,
Miao Xie <miaoxie@...wei.com>
Subject: Re: [PATCH 04/10] staging: erofs: fix
`erofs_workgroup_{try_to_freeze, unfreeze}'
Hi Greg,
On 2018/11/22 19:05, Greg Kroah-Hartman wrote:
> As I said in another email, doing two things with one variable is odd as
> those are two different types of functions.
I think lockref_put_or_lock do the similar thing, it is heavily used in dcache.c, but
1) 0 is special for us, we need lock it on a < 0 value rather than 0.
2) spinlock_t is too large for us because every compressed page will have the structure,
but the locking rarely happens.
Thanks,
Gao Xiang
>
> greg k-h
Powered by blists - more mailing lists