public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John Hawkes" <hawkes@sgi.com>
To: "Robert Love" <rml@novell.com>,
	"John McCutchan" <ttb@tentacle.dhs.org>,
	"John Hawkes" <hawkes@tomahawk.engr.sgi.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-mm3 scaling problem with inotify
Date: Fri, 14 Jan 2005 10:05:21 -0800	[thread overview]
Message-ID: <002301c4fa63$9d9d3b10$6900a8c0@comcast.net> (raw)
In-Reply-To: 1105669742.6027.243.camel@localhost

From: "Robert Love" <rml@novell.com>
...
> John Hawkes: Attached patch implements the dget() optimization in the
> same manner as dnotify.  Compile-tested but not booted.
>
> Let me know!
...
> inotify: don't do dget() unless we have to
>
>  drivers/char/inotify.c |   14 +++++++++++---
>  1 files changed, 11 insertions(+), 3 deletions(-)

The patch shows a substantial 4x improvement for my specific workload (@64p),
although I can still envision workloads that will stimulate high spinlock
contention from spin_lock(&dentry->d_lock).  First things first -- let's get
this fix into the -mm tree.  Thanks!

John Hawkes


  reply	other threads:[~2005-01-14 18:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13 23:56 2.6.10-mm3 scaling problem with inotify John Hawkes
2005-01-14  0:49 ` Robert Love
2005-01-14  1:31   ` John McCutchan
2005-01-14  2:29     ` Robert Love
2005-01-14 18:05       ` John Hawkes [this message]
2005-01-14 18:15         ` Robert Love
2005-01-14 18:39           ` John Hawkes
  -- strict thread matches above, loose matches on Subject: below --
2005-01-14  0:51 John Hawkes
2005-01-14  2:31 Zou, Nanhai
2005-01-14  2:36 ` John McCutchan
2005-01-14  2:41 ` Robert Love

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='002301c4fa63$9d9d3b10$6900a8c0@comcast.net' \
    --to=hawkes@sgi.com \
    --cc=hawkes@tomahawk.engr.sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@novell.com \
    --cc=ttb@tentacle.dhs.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