On Sun, Apr 30, 2000 at 03:57:26PM -0400, Erez Zadok wrote: > It sounds like different people have possibly conflicting needs. I think > any major changes should wait for 2.5. Almost certainly, though there is an argument for cleaning up these APIs now (before we go to 2.4) so that we don't have to change them again too much in 2.5/6. OTOH, if it's going to cause problems for existing code (nfs, and external modules like the stacking stuff) then we should wait. > I would also suggest that such > significant VFS changes be discussed on this list so we can ensure that we > can all get what we need out of the VFS. Thanks. Of course :)
- new VFS method sync_page and stacking Erez Zadok
- Re: new VFS method sync_page and stacking Roman V. Shaposhnick
- Re: new VFS method sync_page and stacking Erez Zadok
- Re: new VFS method sync_page and stacking Steve Dodd
- Re: new VFS method sync_page and stackin... Erez Zadok
- Re: new VFS method sync_page and sta... Steve Dodd
- Re: new VFS method sync_page and stackin... Roman V. Shaposhnick
- Re: new VFS method sync_page and sta... Erez Zadok
- Re: new VFS method sync_page an... Roman V. Shaposhnick
- Re: new VFS method sync_pag... Hans Reiser
- Re: new VFS method sync... Roman V. Shaposhnick
- Re: new VFS method sync_page and sta... Steve Dodd
- Re: new VFS method sync_page an... Alexander Viro
- Re: new VFS method sync_pag... Steve Dodd
- Re: new VFS method sync... Roman V. Shaposhnick
- Re: new VFS method sync_page an... Roman V. Shaposhnick