From: Randy Dunlap <rdunlap@xenotime.net>
To: Aaron Faanes <dafrito@gmail.com>
Cc: John McCutchan <john@johnmccutchan.com>,
Robert Love <rlove@rlove.org>, Eric Paris <eparis@parisplace.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] Documentation: Correct a couple missing words in inotify.txt
Date: Sun, 24 Apr 2011 17:53:18 -0700 [thread overview]
Message-ID: <20110424175318.9e0763cd.rdunlap@xenotime.net> (raw)
In-Reply-To: <1303691704-5726-3-git-send-email-dafrito@gmail.com>
On Sun, 24 Apr 2011 19:35:03 -0500 Aaron Faanes wrote:
> Signed-off-by: Aaron Faanes <dafrito@gmail.com>
> ---
> 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 ***
next prev parent reply other threads:[~2011-04-25 0:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 0:35 [PATCH 0/3] Documentation/filesystems/inotify.txt edits Aaron Faanes
2011-04-25 0:35 ` [PATCH 1/3] Documentation: remove some spurious spaces in inotify.txt Aaron Faanes
2011-04-25 0:52 ` Randy Dunlap
2011-04-25 0:35 ` [PATCH 2/3] Documentation: Correct a couple missing words " Aaron Faanes
2011-04-25 0:53 ` Randy Dunlap [this message]
2011-04-25 0:35 ` [PATCH 3/3] Documentation: Reword example about inotify's fd-per-instance design Aaron Faanes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110424175318.9e0763cd.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=dafrito@gmail.com \
--cc=eparis@parisplace.org \
--cc=john@johnmccutchan.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlove@rlove.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®