Made the final example read more clearly by splitting it into a
couple more sentences.
Signed-off-by: Aaron Faanes <dafrito@xxxxxxxxx>
---
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-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
