From: Filippos Giannakos <philipgian@grnet.gr>
To: Josh Durgin <josh.durgin@inktank.com>
Cc: ceph-devel@vger.kernel.org, synnefo-devel@googlegroups.com
Subject: Re: [PATCH 0/2] librados: Add RADOS locks to the C/C++ API
Date: Mon, 03 Jun 2013 15:57:01 +0300 [thread overview]
Message-ID: <51AC929D.6080401@grnet.gr> (raw)
In-Reply-To: <51A8FDB6.3020908@inktank.com>
Hi Josh,
On 05/31/2013 10:44 PM, Josh Durgin wrote:
> On 05/30/2013 06:02 AM, Filippos Giannakos wrote:
>> The following patches export the RADOS advisory locks functionality to
>> the C/C++
>> librados API. The extra API calls added are inspired by the relevant
>> functions
>> of librbd.
>
> This looks good to me overall. I wonder if we should create a new
> library in the future for these kinds of things that are built on top
> of librados. Other generally useful class client operations could go
> there, as well as generally useful things built on top of librados,
> like methods for striping over many objects.
Thanks for the review. I will incorporate all your suggestions in a new
patch, which I will submit shortly.
As for the new library you mention, it is a good idea, but for now I
think that the basic RADOS locking functionality should be at the core
librados API.
King Regards,
--
Filippos.
<philipgian@grnet.gr>
prev parent reply other threads:[~2013-06-03 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 13:02 [PATCH 0/2] librados: Add RADOS locks to the C/C++ API Filippos Giannakos
2013-05-30 13:02 ` [PATCH 1/2] Add RADOS lock mechanism to the librados " Filippos Giannakos
2013-05-31 19:45 ` Josh Durgin
2013-05-30 13:02 ` [PATCH 2/2] Add RADOS API lock tests Filippos Giannakos
2013-05-31 19:50 ` Josh Durgin
2013-05-31 19:44 ` [PATCH 0/2] librados: Add RADOS locks to the C/C++ API Josh Durgin
2013-06-03 12:57 ` Filippos Giannakos [this message]
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=51AC929D.6080401@grnet.gr \
--to=philipgian@grnet.gr \
--cc=ceph-devel@vger.kernel.org \
--cc=josh.durgin@inktank.com \
--cc=synnefo-devel@googlegroups.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.