mirror of
https://github.com/gluster/glusterfs.git
synced 2026-02-06 18:48:16 +01:00
38bbf50d53
The current API for byte-range locks [glfs_posix_lock()] doesn't allow applications to specify whether it is advisory or mandatory type locks. This particular change is to introduce an extended byte-range lock API with an additional argument for including the byte-range lock mode to be one among advisory(default) or mandatory. Patch also includes a gfapi test case which make use of this new api to acquire mandatory locks. Ref: https://github.com/gluster/glusterfs-specs/blob/master/done/GlusterFS%203.8/Mandatory%20Locks.md Change-Id: Ia09042c755d891895d96da857321abc4ce03e20c Updates #393 Signed-off-by: Anoop C S <anoopcs@redhat.com>
23 lines
562 B
Makefile
23 lines
562 B
Makefile
## compiles against the *system* version of libgfapi,
|
|
## but not the libgfapi for the testcases
|
|
|
|
CFLAGS = -Wall -g $(shell pkg-config --cflags glusterfs-api)
|
|
LDFLAGS = $(shell pkg-config --libs glusterfs-api)
|
|
|
|
BINARIES = upcall-cache-invalidate libgfapi-fini-hang anonymous_fd seek \
|
|
bug1283983 bug1291259 gfapi-ssl-test gfapi-load-volfile \
|
|
mandatory-lock-optimal
|
|
|
|
%: %.c
|
|
$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
|
|
|
|
all: check-pkgconfig $(BINARIES)
|
|
|
|
clean:
|
|
-$(RM) $(BINARIES)
|
|
|
|
.phony: check-pkgconfig
|
|
|
|
check-pkgconfig:
|
|
pkg-config --exists glusterfs-api
|