[TUHS] Were cron and at done at the same time? Or one before the other? [ really linux and filesystems ]

Jon Steinhart jon at fourwinds.com
Mon Dec 14 05:06:06 AEST 2020


Theodore Y. Ts'o writes:
> On Sat, Dec 12, 2020 at 07:07:15PM -0800, Jon Steinhart wrote:
> > Theodore Y. Ts'o writes:
> > > > And, if you can actually make a better file system, please go for it, you're
> > > > a better person than me.  I've looked that that code, and it's huge, has no
> > > > clearly defined entry and exit points, and is undocumented.  While I've been
> > > > too busy to deal with stuff, I found some minor bugs and a possible big
> > > > performance improvement just from trying to read the code.
> > >
> > > Did you report those bugs and potential performance improements?
> > > Feedback is always gratefully accepted.
> > >
> > > As far as documentation is concerned, it's not perfect, but it's
> > > certainly not completely undocumented:
> > >
> > > https://www.kernel.org/doc/html/latest/filesystems/index.html
> > > ...
> > 
> > And sorry, I wasn't clear.  I wasn't talking about the code for a
> > particular filesystem, I was talking about the generic filesystem
> > code.
>
> It's certainly not perfect; if you'd like to suggest improvements,
> again, they would be gratefully accepted, the first link I sent you
> was documentation for the generic file system code, and while there is
> certainly more that I'd love to see documented (improvements and bug
> reports gratefully accepted), the entry points are certainly one of
> the things that is quite well defined:
>
> https://www.kernel.org/doc/html/latest/filesystems/vfs.html
>
> Cheers,
>
> 					- Ted

This isn't really on-topic for TUHS so I'll give you a longer answer by
private email.  Yes, I agree that there is documentation for parts of the
code, some of which even refers to the current version.  Been through a
good pile of it.  Still no clue as to the entry points in namei.c.

Jon


More information about the TUHS mailing list