From: "J. Bruce Fields" <bfields@fieldses.org>
To: Tigran Mkrtchyan <kofemann@googlemail.com>
Cc: linux-nfs@vger.kernel.org, Tigran Mkrtchyan <kofemann@gmail.com>
Subject: Re: [PATH v5 0/8] process current stateid
Date: Mon, 9 Jan 2012 17:56:19 -0500 [thread overview]
Message-ID: <20120109225619.GA17604@fieldses.org> (raw)
In-Reply-To: <1325843116-20570-1-git-send-email-tigran.mkrtchyan@desy.de>
On Fri, Jan 06, 2012 at 10:45:08AM +0100, Tigran Mkrtchyan wrote:
> From: Tigran Mkrtchyan <kofemann@gmail.com>
>
> Yet another update (v5) of current stateid handling
>
> re-based to Benny's git branch pnfs-all-latest ( to include PNFS operations )
>
> Includes a patch from Bruce f32f3c2d3f09a586349ca9180885dc8741290fd9
>
> I have tested:
>
> OPEN+READ+CLOSE
> OPEN+WRITE+CLOSE
> OPEN+LOCK+WRITE+LOCKU+CLOSE
> OPEN+PUTROOTFH+CLOSE
Thanks, Tigran!
How far are we from being done? I think some more operations still need
handling (as in e.g.
http://article.gmane.org/gmane.linux.nfs/45593/match=current+stateid
).
I don't think we have to have pynfs tests for every single of of those,
as they're mostly pretty similar.
When it's ready to be merged, I'd like it rebased on my tree
(git://linux-nfs.org/~bfields/linux.git, for-next branch is fine),
without any of the pNFS bits initially.
--b.
>
>
> implemented but not tested
> OPEN+LAYOUTGET
>
> Tigran.
>
> Tigran Mkrtchyan (8):
> nfsd4: initialize special stateid's at compile time
> nfsd41: handle current stateid in open and close
> nfsd41: handle current stateid on lock and locku
> nfsd41: consume current stateid on read and write
> nfsd41: mark PUTFH, PUTPUBFH and PUTROOTFH to clear current stateid
> nfsd41: save and restore current stateid with current fh
> nfsd41: mark LOOKUP, LOOKUPP and CREATE to invalidate current stateid
> nfsv41: handle current stateid on LAYOUTGET
>
> fs/nfsd/current_stateid.h | 23 +++++++++++
> fs/nfsd/nfs4proc.c | 53 ++++++++++++++++++++-----
> fs/nfsd/nfs4state.c | 95 ++++++++++++++++++++++++++++++++++++++++++--
> fs/nfsd/xdr4.h | 2 +
> 4 files changed, 158 insertions(+), 15 deletions(-)
> create mode 100644 fs/nfsd/current_stateid.h
>
> --
> 1.7.7.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-09 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 9:45 [PATH v5 0/8] process current stateid Tigran Mkrtchyan
2012-01-06 9:45 ` [PATH v5 1/8] nfsd4: initialize special stateid's at compile time Tigran Mkrtchyan
2012-01-06 9:45 ` [PATH v5 2/8] nfsd41: handle current stateid in open and close Tigran Mkrtchyan
2012-01-06 9:45 ` [PATH v5 3/8] nfsd41: handle current stateid on lock and locku Tigran Mkrtchyan
2012-01-06 9:45 ` [PATH v5 4/8] nfsd41: consume current stateid on read and write Tigran Mkrtchyan
2012-01-06 9:45 ` [PATH v5 5/8] nfsd41: mark PUTFH, PUTPUBFH and PUTROOTFH to clear current stateid Tigran Mkrtchyan
2012-01-06 9:45 ` [PATH v5 6/8] nfsd41: save and restore current stateid with current fh Tigran Mkrtchyan
2012-01-06 9:45 ` [PATH v5 7/8] nfsd41: mark LOOKUP, LOOKUPP and CREATE to invalidate current stateid Tigran Mkrtchyan
2012-01-06 9:45 ` [PATH v5 8/8] nfsv41: handle current stateid on LAYOUTGET Tigran Mkrtchyan
2012-01-09 22:56 ` J. Bruce Fields [this message]
2012-01-10 21:54 ` [PATH v5 0/8] process current stateid Tiramisu Mokka
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=20120109225619.GA17604@fieldses.org \
--to=bfields@fieldses.org \
--cc=kofemann@gmail.com \
--cc=kofemann@googlemail.com \
--cc=linux-nfs@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).