From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Frysinger Subject: Re: [RFC][PATCH 0/2] glibc: header file and manual updates for file-private locks Date: Sun, 16 Feb 2014 03:27:05 -0500 Message-ID: <2582214.4RaFrulCEQ@vapier> References: <1392145436-13983-1-git-send-email-jlayton@redhat.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4075176.DSBd15nCcO"; micalg="pgp-sha1"; protocol="application/pgp-signature" Cc: Jeff Layton , linux-fsdevel@vger.kernel.org To: libc-alpha@sourceware.org Return-path: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org In-Reply-To: <1392145436-13983-1-git-send-email-jlayton@redhat.com> List-Id: linux-fsdevel.vger.kernel.org --nextPart4075176.DSBd15nCcO Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" On Tuesday, February 11, 2014 14:03:54 Jeff Layton wrote: > I've been working on a set of patches to add a new type file record l= ock > to the Linux kernel that have less troublesome semantics on close and= > that are usable by threaded applications. >=20 > I have a blog post here with more details: >=20 > =20 > http://jtlayton.wordpress.com/2014/01/07/file-private-posix-locks-aka= =2Dun-po > six-locks/ >=20 > ...and the latest kernel patchset is here: >=20 > https://lkml.org/lkml/2014/1/14/554 >=20 > 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. >=20 > I'm currently shooting for a merge in v3.15 kernel so I'm posting thi= s > as an RFC for now. disclaimer: haven't read the kernel patches. just the patch summary an= d your=20 blog post. looks like the new API manipulates the existing POSIX lock only -- floc= k based=20 locks are still parallel. too crazy to have the new API grab both sinc= e=20 you're bringing proper semantics that cover both ? a good summary of Linux locking from the perspective of userspace was p= osted=20 here sometime ago: =09http://0pointer.de/blog/projects/locking.html random notes/limitations/bugs are also in the various man pages like fc= ntl(2) would be nice if we could cover as many known limitations as possible w= ith the=20 new api so as to not need yet another in the future ;) =2Dmike --nextPart4075176.DSBd15nCcO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAABAgAGBQJTAHZZAAoJEEFjO5/oN/WBat0QANeNVt2EsePddealgPHSjk6d QKSSqcx6UD4ReSOuJA0tjgrAma7hbKimIb+pXQ+08ydxfIM7A/qb22Jws+Xe964c DKgpmqb1GI2NVImbSPtwAXRXhOJja9kR7AS1bunSJAamJvlsU85Ab1J51PQZ3juu ZVhcNEZoGR08B7WAku3y4HjV353lpwVX37klhaAPWDF+O/snYkeywCLqOuScPp9/ r9EfrFT4QFOmu8Jr0WYnED1l3xX6GNqkbbsG3a25idcBha+xs8v4WUmbNg7+hC0V yGppqxdnU0Hxtm0huTjcBCmrs7nAsNZYzli7zcV+nlCH41Iw/v8FWneB8Z82Kw4x XQr3pqji7hIj5r98kaUtXOOhaEDYG6M1FpDdowA5/uVlLjCMgdsr8kxE6gHGI15T q6BZB+xr1faAZaX7eSBzP/i2S2on/PYE+itQogUuqSvct20cPpv9I6n1iDkxeHjZ xoYXm2kaH/IoQYTCmSBBJlYcyhpyQmc/OmQikxPN7FOh1j3oFamoAC8eZFvTZgTM /p+efGpCtd/6MIA2hxA/wnJx5skMUPjAsdn/lCVmR+hwgYFJO3GrfLn+/ZqqNYgO 531PERtL47NqScG0CDnScbPbn71b/znq2HjVNbjlHy5tcdCAJFxjFPQkozZyyBNT dJNtTottQi0UNye+cOk6 =lG+2 -----END PGP SIGNATURE----- --nextPart4075176.DSBd15nCcO--