public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Newall <davidn@davidnewall.com>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	john@johnmccutchan.com, arnd@arndb.de, mtk.manpages@gmail.com,
	hch@lst.de, rlove@rlove.org, linux-api@vger.kernel.org,
	linux-kernel@vger.kernel.org, pavel@suse.cz,
	Eric Paris <eparis@redhat.com>
Subject: Re: [take2] Inotify: nested attributes support.
Date: Wed, 26 Nov 2008 23:33:35 +1030	[thread overview]
Message-ID: <492D4927.8040204@davidnewall.com> (raw)
In-Reply-To: <20081126125113.GA8921@ioremap.net>

Evgeniy Polyakov wrote:
> On Wed, Nov 26, 2008 at 11:17:28PM +1030, David Newall (davidn@davidnewall.com) wrote:
>   
>> I don't think so.  As discussed,
>> (http://marc.info/?l=linux-kernel&m=122735413932519), you already can
>> differentiate I/O made by local users, so you don't need to modify inotify.
>>     
>
> And as was shown it does not work for all cases and introduces unneded
> performance overhead.
>   

If the performance using a local loopback is insufficient, or even when
using a UNIX domain socket, then it's going to be even worse for the
actual network-connected clients.  And the cases were it doesn't work
amount to poor system administration, which is a solvable problem.


>> This change violates my first rule of programming: If there's two or
>> more ways of solving a problem, pick one; don't pick them all.
>>     
>
> Then we should go back to caves, raw meat was so tasty...

Amusing, but irrelevant to programming.

  reply	other threads:[~2008-11-26 13:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 19:42 [take2] Inotify: nested attributes support Evgeniy Polyakov
2008-11-25 19:44 ` [take2] Inotify: nested attributes test application Evgeniy Polyakov
2008-11-26  0:24 ` [take2] Inotify: nested attributes support Andrew Morton
2008-11-26  7:42   ` Evgeniy Polyakov
2008-11-26  8:15     ` Andrew Morton
2008-11-26  8:29       ` Evgeniy Polyakov
2008-11-26  8:38         ` Andrew Morton
2008-11-26  8:46           ` Evgeniy Polyakov
2008-11-26 12:47         ` David Newall
2008-11-26 12:51           ` Evgeniy Polyakov
2008-11-26 13:03             ` David Newall [this message]
2008-11-26 13:15               ` Evgeniy Polyakov
2008-12-04  8:43         ` Pavel Machek
2008-12-04  9:09           ` Evgeniy Polyakov

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=492D4927.8040204@davidnewall.com \
    --to=davidn@davidnewall.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=eparis@redhat.com \
    --cc=hch@lst.de \
    --cc=john@johnmccutchan.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=pavel@suse.cz \
    --cc=rlove@rlove.org \
    --cc=zbr@ioremap.net \
    /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