On Fri, Feb 6, 2015 at 11:39 AM, Xavier Roche <roche+kml2@xxxxxxxxxxx> wrote:
> I'm not sure this is the right place to post, so do not hesitate to redirect me to a more appropriate list if necessary!
You're in the right place!
> New to ceph, I naively attempted to add a flock (int ceph_flock(struct ceph_mount_info *cmount, int fd, int operation)) function in libcephfs, but I could not find the proper way to figure out what was the owner identifier used by Client::ll_flock() (an uint64_t integer) - this is not the pid, I presume ?
You should let the caller pass in the owner ID. For example, if you
were using libcephfs to implement a filesystem interface, it would be
up to that interface to work out the unique ID from the calling layer
above it. So you can pass it through libcephfs, no logic needed.
> Thanks in advance for any hints! By the way - would this new feature (flock()) make sense ?
Definitely, the flock support in the userspace client is new, and the
libcephfs bindings just didn't catch up yet: it was added in October:
commit a1b2c8ff955b30807ac53ce6bdc97cf61a7262ca
Author: Yan, Zheng <zyan@xxxxxxxxxx>
Date: Thu Oct 2 19:07:41 2014 +0800
client: posix file lock support
Signed-off-by: Yan, Zheng <zyan@xxxxxxxxxx>
Cheers,
John
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
