diff options
| author | Anoop C S <anoopcs@redhat.com> | 2016-01-19 14:35:18 +0530 |
|---|---|---|
| committer | Niels de Vos <ndevos@redhat.com> | 2018-01-22 09:54:02 +0000 |
| commit | ec3df9e65a3a2e1005cd4d50d06a8819fd3ab5f6 (patch) | |
| tree | 847ac98b10927e4e1081ba35260beb4b18996d47 /tests/basic/gfapi/Makefile | |
| parent | 10d74166f17fa44c06bd1357e0a4b0b052265425 (diff) | |
libgfapi: Add new api for supporting mandatory-locks
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>
Diffstat (limited to 'tests/basic/gfapi/Makefile')
| -rw-r--r-- | tests/basic/gfapi/Makefile | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/tests/basic/gfapi/Makefile b/tests/basic/gfapi/Makefile index e30fefea5b9..1c5cf03ca3d 100644 --- a/tests/basic/gfapi/Makefile +++ b/tests/basic/gfapi/Makefile @@ -5,7 +5,8 @@ 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 + bug1283983 bug1291259 gfapi-ssl-test gfapi-load-volfile \ + mandatory-lock-optimal %: %.c $(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ |