From: David Weber <wb@munzinger.de>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [RFC] ocfs2/dlm: support range lock
Date: Wed, 28 Jan 2015 08:43:06 +0000 [thread overview]
Message-ID: <0005282F.54C8AF2A@pegasus.munzinger.de> (raw)
Hi,
On 01/26/2015 04:28 AM, yangwenfang wrote:
>
> What:
> Byte range lock is applied to lock a region of a file to accelerate
> reading/writing concurrently.
>
> Why:
> Currently ocfs2 does not support byte range lock. Since multiple nodes
> may concurrently update/write at different positions of the same file
> in database workloads, the performance(tpmc) of DB+ocfs2 is much poorer
> than
> DB+GPFS in running TPCC.
> Aiming at improving the efficiency of parallel accesses to the same file,
> we have implemented a demo of range lock feature which has been supported
> by lustre and GPFS, so that a file can be updated by different nodes in
> the cluster when they are visiting different blocks.
would this also make cluster aware fcntl(2) locks with the o2cb stack possible?
Cheers,
David
next reply other threads:[~2015-01-28 8:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 8:43 David Weber [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-01-26 12:28 [Ocfs2-devel] [RFC] ocfs2/dlm: support range lock yangwenfang
2015-01-27 7:08 ` Srinivas Eeda
2015-01-29 6:42 ` yangwenfang
2015-01-29 11:04 ` Goldwyn Rodrigues
2015-01-30 2:59 ` Xue jiufei
2015-01-30 12:37 ` Goldwyn Rodrigues
2015-01-31 4:15 ` yangwenfang
2015-01-29 11:07 ` Goldwyn Rodrigues
2015-01-29 0:05 ` Goldwyn Rodrigues
2015-01-29 3:21 ` Wengang Wang
2015-01-29 7:47 ` yangwenfang
2015-01-29 8:06 ` Wengang Wang
2015-01-30 3:54 ` yangwenfang
2015-01-30 6:02 ` Wengang Wang
2015-01-30 7:46 ` yangwenfang
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=0005282F.54C8AF2A@pegasus.munzinger.de \
--to=wb@munzinger.de \
--cc=ocfs2-devel@oss.oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.