On Sun, 24 Apr 2011 19:35:03 -0500 Aaron Faanes wrote: > Signed-off-by: Aaron Faanes <dafrito@xxxxxxxxx> > --- > Documentation/filesystems/inotify.txt | 4 ++-- > 1 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/filesystems/inotify.txt b/Documentation/filesystems/inotify.txt > index f00c435..8d8cba1 100644 > --- a/Documentation/filesystems/inotify.txt > +++ b/Documentation/filesystems/inotify.txt > @@ -248,9 +248,9 @@ A: An fd-per-watch quickly consumes more file descriptors than are allowed, > > When you talk about designing a file change notification system that > scales to 1000s of directories, juggling 1000s of fd's just does not seem > - the right interface. It is too heavy. > + to be the right interface. It is too heavy. either way is OK. > > - Additionally, it _is_ possible to more than one instance and > + Additionally, it _is_ possible to have more than one instance and OK, there is the missing word. > juggle more than one queue and thus more than one associated fd. There > need not be a one-fd-per-process mapping; it is one-fd-per-queue and a > process can easily want more than one queue. > -- --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
