From: Jeff Layton <jlayton@redhat.com>
To: libc-alpha@sourceware.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [RFC][PATCH 0/2] glibc: header file and manual updates for file-private locks
Date: Tue, 11 Feb 2014 14:03:54 -0500 [thread overview]
Message-ID: <1392145436-13983-1-git-send-email-jlayton@redhat.com> (raw)
I've been working on a set of patches to add a new type file record lock
to the Linux kernel that have less troublesome semantics on close and
that are usable by threaded applications.
I have a blog post here with more details:
http://jtlayton.wordpress.com/2014/01/07/file-private-posix-locks-aka-un-posix-locks/
...and the latest kernel patchset is here:
https://lkml.org/lkml/2014/1/14/554
This patchset represents a set of corresponding updates for glibc. It
just adds the new cmd values to fcntl.h, and a manual update that
discusses how to use the new locks.
I'm currently shooting for a merge in v3.15 kernel so I'm posting this
as an RFC for now.
Comments and suggestions appreciated...
Thanks,
Jeff Layton (2):
fcntl.h: add new definitions for file-private lock cmd values
manual: update manual to document file-private locks
ChangeLog | 5 +
manual/llio.texi | 175 ++++++++++++++++++++++++++++-
sysdeps/unix/sysv/linux/bits/fcntl-linux.h | 18 +++
3 files changed, 196 insertions(+), 2 deletions(-)
--
1.8.5.3
next reply other threads:[~2014-02-11 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 19:03 Jeff Layton [this message]
2014-02-11 19:03 ` [RFC][PATCH 1/2] fcntl.h: add new definitions for file-private lock cmd values Jeff Layton
2014-02-11 21:49 ` Roland McGrath
2014-02-11 23:57 ` Jeff Layton
2014-02-12 7:50 ` Andreas Schwab
2014-02-12 23:19 ` Roland McGrath
2014-02-11 19:03 ` [RFC][PATCH 2/2] manual: update manual to document file-private locks Jeff Layton
2014-02-16 8:27 ` [RFC][PATCH 0/2] glibc: header file and manual updates for " Mike Frysinger
2014-02-16 12:42 ` Jeff Layton
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=1392145436-13983-1-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).