[pnfs] linux-pnfs-2.6-latest file layout data serversessionmanagement

[William A. (Andy) Adamson]

On 10/16/07, Muntz, Daniel <Dan.Muntz at netapp.com> wrote:
>
> Comments inline...
>
> > -----Original Message-----
> > From: Iyer, Rahul
> > Sent: Tuesday, October 16, 2007 1:23 PM
> > To: William A. (Andy) Adamson; pnfs at linux-nfs.org
> > Subject: Re: [pnfs] linux-pnfs-2.6-latest file layout data
> > serversessionmanagement
> >
> > Comments inline...
> >
> >
> > >
> > >
> > > Questions
> > > ---------
> > >
> > > 1) should we plan for multiple sessions to a data server?
> > >
> >
> > Why would we do multiple sessions? I can understand multiple
> > connections
> > over the same session...
>
> What if we have a data server acting as a DS for multiple MDSs?  I
> assumed we would want support for multiple sessions.


true.  the data server structs are per FSID (per mds nfs_server). so if the
same data server is used
for more than one FSID, there will be a data server struct hanging off each
fsid. so the design can handle this
situation.

-->Andy

-->Andy

>
> > > 2) we could create a new struct to hold only exchange id and
> > > client id bookeeping.
> > > this would mean changing the interface to
> > > nfs4_proc_exchange_id, and to nfs4_state_recovery_ops. not worth it?
> > >
> > Yes and no. For the short term, in the interest of getting stuff up to
> > speed asap so that everyone can develop on the new client, I
> > think using
> > an nfs_client struct per data server is the way to go. In the
> > long term
> > however, I do believe we should use something more consise. nfs_client
> > has way too much unnecessary information to be used for a DS
> > representation.
> >
> > -Rahul
> > _______________________________________________
> > pNFS mailing list
> > pNFS at linux-nfs.org
> > http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://linux-nfs.org/pipermail/pnfs/attachments/20071016/87d39d34/attachment.htm