From: Dave Chinner <email@example.com> To: Davidlohr Bueso <firstname.lastname@example.org> Cc: Jan Kara <email@example.com>, Amir Goldstein <firstname.lastname@example.org>, "Darrick J . Wong" <email@example.com>, Christoph Hellwig <firstname.lastname@example.org>, Matthew Wilcox <email@example.com>, firstname.lastname@example.org, email@example.com Subject: Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload Date: Thu, 11 Apr 2019 11:11:17 +1000 [thread overview] Message-ID: <20190411011117.GC29573@dread.disaster.area> (raw) In-Reply-To: <firstname.lastname@example.org> On Mon, Apr 08, 2019 at 09:37:09AM -0700, Davidlohr Bueso wrote: > On Mon, 2019-04-08 at 12:33 +0200, Jan Kara wrote: > > On Fri 05-04-19 08:17:30, Dave Chinner wrote: > > > FYI, I'm working on a range lock implementation that should both > > > solve the performance issue and the reader starvation issue at the > > > same time by allowing concurrent buffered reads and writes to > > > different file ranges. > > > > Are you aware of range locks Davidlohr has implemented ? It didn't get > > merged because he had no in-tree user at the time (he was more aiming at > > converting mmap_sem which is rather difficult). But the generic lock > > implementation should be well usable. > > > > Added Davidlohr to CC. > > > > Honza > > > >  https://lkml.org/lkml/2017/3/7/22 > > fyi this was the latest version (had some naming updates per peterz). > > https://lkml.org/lkml/2018/2/4/232 No, I wasn't aware of these because they haven't ever been posted to a list I subscribe to and they haven't been merged. I'll go have a look at them over the next few days. Cheers, Dave. -- Dave Chinner email@example.com
next prev parent reply other threads:[~2019-04-11 1:31 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-04-04 16:57 Amir Goldstein 2019-04-04 21:17 ` Dave Chinner 2019-04-05 14:02 ` Amir Goldstein 2019-04-07 23:27 ` Dave Chinner 2019-04-08 9:02 ` Amir Goldstein 2019-04-08 14:11 ` Jan Kara 2019-04-08 17:41 ` Amir Goldstein 2019-04-09 8:26 ` Jan Kara 2019-04-08 11:03 ` Jan Kara 2019-04-22 10:55 ` Boaz Harrosh 2019-04-08 10:33 ` Jan Kara 2019-04-08 16:37 ` Davidlohr Bueso 2019-04-11 1:11 ` Dave Chinner [this message] 2019-04-16 12:22 ` Dave Chinner 2019-04-18 3:10 ` Dave Chinner 2019-04-18 18:21 ` Davidlohr Bueso 2019-04-20 23:54 ` Dave Chinner 2019-05-03 4:17 ` Dave Chinner 2019-05-03 5:17 ` Dave Chinner
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=20190411011117.GC29573@dread.disaster.area \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [POC][PATCH] xfs: reduce ilock contention on buffered randrw workload' \ /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
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).