From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jon Steinhart <jon@fourwinds.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Were cron and at done at the same time? Or one before the other?
Date: Sun, 13 Dec 2020 11:49:16 -0500 [thread overview]
Message-ID: <20201213164916.GG575698@mit.edu> (raw)
In-Reply-To: <202012130307.0BD37F0U2780521@darkstar.fourwinds.com>
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
next prev parent reply other threads:[~2020-12-13 16:50 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 4:35 M Douglas McIlroy
2020-12-09 15:40 ` Clem Cole
2020-12-09 15:46 ` Niklas Karlsson
2020-12-09 16:01 ` Bakul Shah
2020-12-09 16:11 ` Clem Cole
2020-12-09 17:05 ` Bakul Shah
2020-12-09 17:42 ` Dan Stromberg
2020-12-09 23:46 ` Nemo Nusquam
2020-12-14 20:28 ` Dave Horsfall
2020-12-14 22:23 ` Thomas Paulsen
2020-12-14 23:04 ` Andrew Hume
2020-12-14 23:59 ` Harald Arnesen
2020-12-17 4:08 ` John Cowan
2020-12-15 2:57 ` Bakul Shah
2020-12-15 3:05 ` Warner Losh
[not found] ` <CAC20D2PXZY9aWgDf-RknROs6JbKEUjzbQ2BRzfTgTR07pXni3g@mail.g mail.com>
2020-12-09 16:04 ` John Foust
2020-12-09 16:40 ` Warner Losh
2020-12-09 16:53 ` Jon Steinhart
2020-12-09 16:58 ` Theodore Y. Ts'o
2020-12-09 19:58 ` Dan Cross
2020-12-09 20:30 ` Will Senn
2020-12-13 1:07 ` Theodore Y. Ts'o
2020-12-13 1:56 ` Jon Steinhart
2020-12-13 2:58 ` Theodore Y. Ts'o
2020-12-13 3:07 ` Jon Steinhart
2020-12-13 16:49 ` Theodore Y. Ts'o [this message]
2020-12-13 19:06 ` [TUHS] Were cron and at done at the same time? Or one before the other? [ really linux and filesystems ] Jon Steinhart
2020-12-13 3:02 ` [TUHS] Were cron and at done at the same time? Or one before the other? Dan Cross
2020-12-09 23:22 ` Bakul Shah
2020-12-09 23:44 ` Steffen Nurpmeso
2020-12-09 23:51 ` Steffen Nurpmeso
2020-12-10 0:19 ` [TUHS] Cole's Slaw John Gilmore
2020-12-10 0:29 ` Larry McVoy
2020-12-10 0:53 ` Erik E. Fair
2020-12-10 3:10 ` George Michaelson
2020-12-12 21:11 ` Dave Horsfall
2020-12-10 1:49 ` John Cowan
2020-12-10 2:12 ` Jon Steinhart
2020-12-12 2:56 ` [TUHS] Were cron and at done at the same time? Or one before the other? Dave Horsfall
2020-12-12 19:10 ` scj
-- strict thread matches above, loose matches on Subject: below --
2020-12-13 2:02 Noel Chiappa
2020-12-13 2:08 ` Clem Cole
2020-12-09 19:25 Noel Chiappa
2020-12-08 18:11 ron minnich
2020-12-08 18:51 ` Mary Ann Horton
2020-12-08 19:05 ` Larry McVoy
2020-12-08 19:20 ` Michael Kjörling
2020-12-09 2:00 ` Dave Horsfall
2020-12-08 19:39 ` Clem Cole
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201213164916.GG575698@mit.edu \
--to=tytso@mit.edu \
--cc=jon@fourwinds.com \
--cc=tuhs@tuhs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).