Re: [patch] inotify.

[Andrew Morton]

John McCutchan <ttb@xxxxxxxxxxxxxxxx> wrote:
>
> This was settled a long time ago. Robert, Andrew, and I had an off-list
> discussion months ago, and we all agreed that this was the right
> interface for inotify.

I don't think I ever really affirmatively agreed to anything.  I do recall
various things being discussed at various times and various things being
changed, but from where I sit it's all spread out and foggy.

I certainly remember that good-sounding recommendations which addressed the
things which Christoph doesn't like were convincingly shot down by yourself
and by Robert, but I don't recall why.

Look, this stuff is hard.  This is why I've asked you and Robert again and
again and again to generate some sort of design doc or FAQ which addresses
each of these frequently-asked-questions.  So the poor rest of us can look
through it and say "oh yeah".  Because inotify _is_ a tricky thing, and
standard kernel interface designs _don't_ fit it well.

So.  It's not too late.  Please spend an hour and write up the Inofity
Implementation FAQ?  You probably remember and fully understand what all of
our objections are and I know that you have explanations and rebuttals at
hand.

Please?  Something like:

q: Why does it use an ioctl multiplexer

a: Because ...

etc...

I haven't done a detailed review of the patch in months and I intend to do
another soon.  That FAQ will help!  When I ask more silly questions we can
update it, so those questions will never again be asked.

I know it's unusual process-wise, but inotify is an unusual feature.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/