From: Ming Lei <ming.lei@redhat.com>
To: YangYang <yang.yang@vivo.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <axboe@kernel.dk>, Omar Sandoval <osandov@fb.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org
Subject: Re: [PATCH v6] sbitmap: fix io hung due to race on sbitmap_word::cleared
Date: Thu, 11 Jul 2024 21:39:06 +0800 [thread overview]
Message-ID: <Zo/gevNqftePGvic@fedora> (raw)
In-Reply-To: <ead047aa-d9dc-4b2f-869f-610b309b5092@vivo.com>
On Thu, Jul 11, 2024 at 08:48:03PM +0800, YangYang wrote:
> On 2024/7/11 3:54, Bart Van Assche wrote:
> > On 7/9/24 11:56 PM, Yang Yang wrote:
> > > + /**
> > > + * @swap_lock: Held while swapping word <-> cleared
> > > + */
> > > + spinlock_t swap_lock;
> >
> > Why is only swapping 'word' with 'cleared' protected by the spinlock?
> > If all 'cleared' changes would be protected by this spinlock then
> > that would allow to eliminate the expensive xchg() call from
> > sbitmap_deferred_clear().
>
> The spinlock was initially introduced in ea86ea2cdced ("sbitmap:
> ammortize cost of clearing bits").
> I think if all 'cleared' changes are protected by the spinlock, the
> overhead of clearing tags would definitely increase.
There are only two WRITE on 'cleared':
- xchg(&map->cleared, 0) in sbitmap_deferred_clear()
- set_bit() in sbitmap_deferred_clear_bit()
xchg() supposes to provide such protection already.
Thanks,
Ming
next prev parent reply other threads:[~2024-07-11 13:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 6:56 [PATCH v6] sbitmap: fix io hung due to race on sbitmap_word::cleared Yang Yang
2024-07-10 16:41 ` Bart Van Assche
2024-07-11 9:47 ` YangYang
2024-07-10 19:54 ` Bart Van Assche
2024-07-11 12:48 ` YangYang
2024-07-11 13:39 ` Ming Lei [this message]
2024-07-11 16:33 ` Bart Van Assche
2024-07-12 1:01 ` Ming Lei
2024-07-12 17:53 ` Bart Van Assche
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=Zo/gevNqftePGvic@fedora \
--to=ming.lei@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osandov@fb.com \
--cc=yang.yang@vivo.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