[OpenAFS-devel] byte-range locking

[Neulinger, Nathan]

Yes, it's been discussed several times, and yes, it should almost
certainly work, please read the list archives and twiki.

No, patches don't exist. Most useful platform is windows, and I don't
have much interest in developing for it.=20

Patches would certainly be welcomed on the windows side since it is so
negatively impacted by the lack of byte range locks.=20

-- Nathan

------------------------------------------------------------
Nathan Neulinger                       EMail:  nneul@umr.edu
University of Missouri - Rolla         Phone: (573) 341-6679
UMR Information Technology             Fax: (573) 341-4216
=20

> -----Original Message-----
> From: openafs-devel-admin@openafs.org=20
> [mailto:openafs-devel-admin@openafs.org] On Behalf Of Joe Buehler
> Sent: Monday, September 20, 2004 9:02 AM
> To: openafs-devel@openafs.org
> Subject: [OpenAFS-devel] byte-range locking
>=20
> If I understand the existing code correctly, a server process
> (I don't know which one -- fileserver?) keeps track of=20
> clients that have
> exclusive or non-exclusive locks on a file.  Clients are
> responsible for keeping track of which processes have such locks.
>=20
> So it looks as though it should be easy to add local byte-range
> locking for processes on a single machine.  Read locks would be
> propagated to the server as shared locks, and write locks would
> propagate as exclusive locks, and the byte ranges would be
> handled in the local client kernel code.
>=20
> Does someone already have patches for this perhaps?
> --=20
> Joe Buehler
>=20
> _______________________________________________
> OpenAFS-devel mailing list
> OpenAFS-devel@openafs.org
> https://lists.openafs.org/mailman/listinfo/openafs-devel
>=20
>=20