From: Andy Adamson <andros@thnk.citi.umich.edu>
To: linux-fsdevel@vger.kernel.org
Cc: nfsv4@linux-nfs.org, willy@debian.org
Subject: [PATCH 0 of 10] RESEND: lease interfaces for version 4 NFSD
Date: Tue, 21 Sep 2004 18:35:35 -0400 [thread overview]
Message-ID: <1095804047.21441d5b.1@citi.umich.edu> (raw)
I'm resending these 10 patches, following Matthew Wilcoxs advice on kernel coding style. I broke down and used Andrew Morton's patch management scripts - very cool. I apologize for the resend...
The following patches provide an interface to the lease subsystem in the
current VFS locking code.
The version 4 nfsd delegation implementation uses leases to co-ordinate
behavior between local, samba, and nfs access.
The main design points are
- Seperate the file_lock processing from the file descriptor processing in
fcntl_setlease.
- New non-file descriptor interface to setlease
- Use new lock manager callbacks to allow nfsd to create, break, and release
leases.
- Provide default lock manager callbacks for fcntl_setlease
-->Andy Adamson
reply other threads:[~2004-09-21 22:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1095804047.21441d5b.1@citi.umich.edu \
--to=andros@thnk.citi.umich.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=willy@debian.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).