From: David Chinner <dgc@sgi.com>
To: Kentaro Makita <k-makita@np.css.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org, dgc@sgi.com, viro@ZenIV.linux.org.uk,
harvey.harrison@gmail.com
Subject: Re: [PATCH][RFC]fix soft lock up at NFS mount by per-SB LRU-list of unused dentries
Date: Fri, 23 May 2008 14:22:31 +1000 [thread overview]
Message-ID: <20080523042231.GJ173056135@sgi.com> (raw)
In-Reply-To: <483628B7.1080704@np.css.fujitsu.com>
On Fri, May 23, 2008 at 11:15:19AM +0900, Kentaro Makita wrote:
> Hi, David
>
> Thank you for reviewing the patch.
> I'd fix coding style issues at next post. And,...
>
> David Chinner wrote:
> > On Thu, May 22, 2008 at 11:22:18AM +0900, Kentaro Makita wrote:
> >> + }
> >> + }
> >> + }
> >
> > I'm wondering if this loop is an excessively long time to be holding the
> > dcache_lock. I guess the hol dtime is limited by the size of *count being
> > passed in. I think we could also do a:
> >
> > cond_resched_lock(&dcache_lock);
> >
> > in the loop here to prevent this from occurring....
> Did you mean:
> - scan sb->s_dentry_lru and move dentries to temporary list
> with lock held
> - cond_resched_lock(&dcache_lock);
> - prune dentries on temporary list
> Is that right?
No, I meant while scanning sb->s_dentry_lru.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2008-05-23 4:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 2:22 [PATCH][RFC]fix soft lock up at NFS mount by per-SB LRU-list of unused dentries Kentaro Makita
2008-05-22 6:55 ` Andrew Morton
2008-05-22 8:20 ` Kentaro Makita
2008-05-22 22:56 ` David Chinner
2008-05-22 23:14 ` Harvey Harrison
2008-05-23 2:15 ` Kentaro Makita
2008-05-23 4:22 ` David Chinner [this message]
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=20080523042231.GJ173056135@sgi.com \
--to=dgc@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=k-makita@np.css.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.