[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1303691704-5726-4-git-send-email-dafrito@gmail.com>
Date: Sun, 24 Apr 2011 19:35:04 -0500
From: Aaron Faanes <dafrito@...il.com>
To: John McCutchan <john@...nmccutchan.com>,
Robert Love <rlove@...ve.org>,
Eric Paris <eparis@...isplace.org>
Cc: Randy Dunlap <rdunlap@...otime.net>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, Aaron Faanes <dafrito@...il.com>
Subject: [PATCH 3/3] Documentation: Reword example about inotify's fd-per-instance design
Made the final example read more clearly by splitting it into a
couple more sentences.
Signed-off-by: Aaron Faanes <dafrito@...il.com>
---
Documentation/filesystems/inotify.txt | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/filesystems/inotify.txt b/Documentation/filesystems/inotify.txt
index 8d8cba1..fbb50ad 100644
--- a/Documentation/filesystems/inotify.txt
+++ b/Documentation/filesystems/inotify.txt
@@ -246,9 +246,9 @@ A: An fd-per-watch quickly consumes more file descriptors than are allowed,
- 1024 is still too low. ;-)
- 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
- to be the right interface. It is too heavy.
+ For example, consider the design of a file change notification system that
+ scales to 1000s of directories. Juggling 1000s of fd's in this case is just
+ not the right interface. It is too heavy.
Additionally, it _is_ possible to have more than one instance and
juggle more than one queue and thus more than one associated fd. There
--
1.7.4.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists