From: David Laight <David.Laight@ACULAB.COM>
To: 'Sahitya Tummala' <stummala@codeaurora.org>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] f2fs: change to use rwsem for cp_mutex
Date: Mon, 23 Nov 2020 17:05:08 +0000 [thread overview]
Message-ID: <7f5213fb9b334d1290f019ab8ed6ee71@AcuMS.aculab.com> (raw)
In-Reply-To: <1606109312-1944-1-git-send-email-stummala@codeaurora.org>
From: Sahitya Tummala
> Sent: 23 November 2020 05:29
>
> Use rwsem to ensure serialization of the callers and to avoid
> starvation of high priority tasks, when the system is under
> heavy IO workload.
I can't see any read lock requests.
So why the change?
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2020-11-23 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 5:28 [PATCH] f2fs: change to use rwsem for cp_mutex Sahitya Tummala
2020-11-23 17:05 ` David Laight [this message]
2020-11-24 3:12 ` Chao Yu
2020-11-24 9:12 ` David Laight
2020-11-25 13:08 ` Sahitya Tummala
2020-11-24 3:06 ` Chao Yu
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=7f5213fb9b334d1290f019ab8ed6ee71@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stummala@codeaurora.org \
--cc=yuchao0@huawei.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;
as well as URLs for NNTP newsgroup(s).