From: Atri Sharma <atri.jiit@gmail.com>
To: Josef Bacik <jbacik@fusionio.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: BTree lock contention
Date: Tue, 18 Dec 2012 19:43:51 +0530 [thread overview]
Message-ID: <CAOeZVidsxcR16t3v6OKU6fAJbB_S64sbQM1CyL2D_t_CtE1ajg@mail.gmail.com> (raw)
In-Reply-To: <20121218140409.GD2403@localhost.localdomain>
Thanks.
I shall mark it as in progress then.
For writer's contention, I was thinking of decreasing the lock
granularity. I have not really thought about it deeply yet, but my
initial plans are to identify areas where we can distribute the locks,
and maybe use techniques such as combining trees.
Thanks a ton,
Atri
On Tue, Dec 18, 2012 at 7:34 PM, Josef Bacik <jbacik@fusionio.com> wrote:
> On Mon, Dec 17, 2012 at 09:24:23PM -0700, Atri Sharma wrote:
>> Hi All,
>>
>> I was looking through the project ideas page for picking up a project
>> do start working with BTRFS. I am really interested in Btree lock
>> contention project, but it seems to be marked that it has already been
>> done in v3.1
>>
>> Is the project still open? Can I work on it?
>>
>
> Go for it, we still have plenty of lock contention, it's just in 3.1 we switched
> to a read/write lock which helped a bunch. Still if you have all writers you
> are going to hit quite a bit of lock contention, especially on the root nodes.
> If you have ideas go for it. Thanks,
>
> Josef
--
Regards,
Atri
l'apprenant
next prev parent reply other threads:[~2012-12-18 14:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 4:24 BTree lock contention Atri Sharma
2012-12-18 14:04 ` Josef Bacik
2012-12-18 14:13 ` Atri Sharma [this message]
2012-12-18 14:27 ` Atri Sharma
2012-12-19 13:17 ` David Sterba
2012-12-19 15:00 ` Atri Sharma
2012-12-19 15:04 ` Atri Sharma
2012-12-19 15:09 ` David Sterba
2012-12-19 15:17 ` Atri Sharma
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=CAOeZVidsxcR16t3v6OKU6fAJbB_S64sbQM1CyL2D_t_CtE1ajg@mail.gmail.com \
--to=atri.jiit@gmail.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
/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).