[pnfs] [PATCH] Removed sessions hard-coded 32678 byte max sizes
Iyer, Rahul
Rahul.Iyer at netapp.com
Fri Mar 16 17:02:46 EDT 2007
The way I see it, the only thing left in the sessions code is:
1. Server side slot table
2. Server/client side callback code
(Anything else?)
Since we're already at 14K lines, these two features might add another
2-3K maybe. If we're gonna wrestle 14K, then 16K might not be a lot more
effort.
That being said, I'll start working on the callback code as soon as I
get the slot table patches split so Andy can merge them. After that I
can start the migration to the latest kernel. I should be done (tested
and stable) by the end of April, I think.
But it is my strong preference to have a stable "Austin event kernel"
before we do the migration.
Regards
Rahul
> -----Original Message-----
> From: Marc Eshel [mailto:eshel at almaden.ibm.com]
> Sent: Friday, March 16, 2007 1:55 PM
> To: J. Bruce Fields
> Cc: pnfs at linux-nfs.org
> Subject: Re: [pnfs] [PATCH] Removed sessions hard-coded 32678
> byte max sizes
>
> If we have a plan that can show that we can do all those
> changes with a new kernel and be ready for bakeathon than I
> would support it. I don't want to go to the bakeathon
> unprepared, in the last connectathon we did not accomplish
> much (with the pNFS testing) because we were not ready. We
> can do it with the risk that we will not make the bakeathon
> which is fine with me, but I will not go to Austin with an
> unstable system.
> Marc.
>
> "J. Bruce Fields" <bfields at fieldses.org> wrote on 03/16/2007
> 01:36:29 PM:
>
> > On Fri, Mar 16, 2007 at 11:49:25AM -0700, Marc Eshel wrote:
> > > I think that the priority should be show a complete
> implementation
> > > for
> the
> > > bakeathon so the draft can verify that the draft is complete and
> > > than
> go
> > > back and reorganize the code for future development on
> latest kernels.
> >
> > The diff from mainline right now is about 14,000 lines
> changed across
> > 74 files. In another 3 months that'll be much larger. Is
> it going to
> > be practical to reorgnize that?
> >
> > Would there be any chance of getting a minimal mainline-ready
> > implementation of sessions ready by the bakeathon? (I
> don't know what
> > the minimum useful functionality would be--would enough to support
> > delegation recalls over NATs be too much?)
> >
> > --b.
>
> _______________________________________________
> pNFS mailing list
> pNFS at linux-nfs.org
> http://linux-nfs.org/cgi-bin/mailman/listinfo/pnfs
>
More information about the pNFS
mailing list