On Wed, 2010-12-15 at 20:51 +0200, Benny Halevy wrote:
> On 2010-12-15 20:32, Trond Myklebust wrote:
> > On Wed, 2010-12-15 at 20:30 +0200, Benny Halevy wrote:
> >> This reverts commit 19e1e5ae1ec0a3f5d997a1a5d924d482e147bea2.
> >> ---
> >> include/linux/nfs4.h | 1 +
> >> include/linux/nfs_xdr.h | 23 +++++++++++++++++++++++
> >> 2 files changed, 24 insertions(+), 0 deletions(-)
> >>
> >> diff --git a/include/linux/nfs4.h b/include/linux/nfs4.h
> >> index 8ca7700..55511e8 100644
> >> --- a/include/linux/nfs4.h
> >> +++ b/include/linux/nfs4.h
> >> @@ -557,6 +557,7 @@ enum {
> >> NFSPROC4_CLNT_RECLAIM_COMPLETE,
> >> NFSPROC4_CLNT_LAYOUTGET,
> >> NFSPROC4_CLNT_LAYOUTCOMMIT,
> >> + NFSPROC4_CLNT_LAYOUTRETURN,
> >> NFSPROC4_CLNT_GETDEVICEINFO,
> >> NFSPROC4_CLNT_PNFS_WRITE,
> >> NFSPROC4_CLNT_PNFS_COMMIT,
> >> diff --git a/include/linux/nfs_xdr.h b/include/linux/nfs_xdr.h
> >> index 9d847ac..a651574 100644
> >> --- a/include/linux/nfs_xdr.h
> >> +++ b/include/linux/nfs_xdr.h
> >> @@ -258,6 +258,29 @@ struct nfs4_layoutcommit_data {
> >> int status;
> >> };
> >>
> >> +struct nfs4_layoutreturn_args {
> >> + __u32 reclaim;
> >> + __u32 layout_type;
> >> + __u32 return_type;
> >> + struct pnfs_layout_range range;
> >> + struct inode *inode;
> >> + struct nfs4_sequence_args seq_args;
> >> +};
> >> +
> >> +struct nfs4_layoutreturn_res {
> >> + struct nfs4_sequence_res seq_res;
> >> + u32 lrs_present;
> >> + nfs4_stateid stateid;
> >> +};
> >> +
> >> +struct nfs4_layoutreturn {
> >> + struct nfs4_layoutreturn_args args;
> >> + struct nfs4_layoutreturn_res res;
> >> + struct rpc_cred *cred;
> >> + struct nfs_client *clp;
> >> + int rpc_status;
> >> +};
> >> +
> >> struct nfs4_getdeviceinfo_args {
> >> struct pnfs_device *pdev;
> >> struct nfs4_sequence_args seq_args;
> >
> > Why? We don't need or even want layoutreturn. It adds too much
> > serialisation crap.
>
> Define "we" :)
Definition: "We who will be forced to maintain whatever is merged
upstream."
> First, the object layout driver relies on layout return for returning I/O error
> information. On the common, successful path, with return_on_close (that Panasas
> uses but others may not) I agree that CLOSE with the implicit layoutreturn
> semantics we discussed should do a good job too (accompanied with a respective
> LAYOUTCOMMIT if needed).
>
> Then, when there's a large number of outstanding layout segments (again
> prob. non-files layout presuming server implementations are going to utilize
> whole-file layouts) proactive layoutreturn comes handy in capping the
> state both the client and server keep - reducing time wasted on walking long
> lists of items.
That assumes that you have a good policy for implementing a 'proactive
layoutreturn'. What knowledge does either the client or the server have
w.r.t. whether or not part of a layout is likely to be used in the near
future other than 'file is open' or 'file is closed'?
What is the advantage to the client w.r.t. sending LAYOUTRETURN rather
than just forgetting the layout or layout segment? If the server needs
it returned, it can send a recall. If not, we are wasting processing
time by sending an unnecessary RPC call.
> For CB_LAYOUTRECALL response the heart of the debate is around synchronizing
> with layouts in-use and in-flight layoutgets. There, having the server poll
> the client, who's retuning NFS4ERR_DELAY should essentially work but may be
> inefficient and unreliable in use cases where contention is likely enough.
Define these use cases. Otherwise we're just talking generalities and
presenting circular arguments again.
> Eventually, when CB_LAYOUTRECALL is clear to go sending the LAYOUTRETURN
> or replying with CB_NOMATCHING_LAYOUT (assuming no I/O error to report
> for pnfs-obj) should be equivalent [note: need errata to clarify the
> resulting stateid after NOMATCHING_LAYOUT].
> Is this the serialization "crap" you're talking about?
> What makes checking the conditions for returning NFS4ERR_DELAY to
> CB_LAYOUTRECALL so different from implementing a barrier and doing the
> returns asynchronously with the CB_LAYOUTRECALL?
"CB_LAYOUTRECALL request processing MUST be processed in "seqid" order
at all times." (section 12.5.3).
In other words, you cannot just 'do the returns asynchronously': the
CB_LAYOUTRECALL requests are required by the protocol to be processed in
order, which means that you must serialise those LAYOUTRETURN calls to
ensure that they all happen in the order the wretched server expects.
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@xxxxxxxxxx
www.netapp.com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
