lkml.org 
[lkml]   [2011]   [Apr]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH 3/3] Documentation: Reword example about inotify's fd-per-instance design
Date
Made the final example read more clearly by splitting it into a
couple more sentences.

Signed-off-by: Aaron Faanes <dafrito@gmail.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


\
 
 \ /
  Last update: 2011-04-25 02:39    [W:0.182 / U:0.360 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site