From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
LINUXFS-ML <linux-fsdevel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
James Bottomley <jbottomley@parallels.com>,
xemul@openvz.org
Subject: Re: [patch 0/3] A few patches for dcache
Date: Fri, 29 Jul 2011 11:01:54 +0400 [thread overview]
Message-ID: <20110729070153.GC15883@sun> (raw)
In-Reply-To: <20110729065951.GE5404@dastard>
On Fri, Jul 29, 2011 at 04:59:51PM +1000, Dave Chinner wrote:
...
> >
> > Thanks for comments, Dave! Still the read only lock without
> > increasing sequence number might be useful, no? (patch 1)
>
> I'll defer to Al on that one - the intricacies of the rename locking
> are way over my head.
ok
>
> FWIW, the problems with the per-sb dcache LRU lock seem to be gone -
> it's not causing my test machines to fall over with the current
> Linus tree like it was during 2.6.39-rc and 3.0-rc kernels...
>
> Cheers,
>
> Dave.
ok, thanks for info!
Cyrill
next prev parent reply other threads:[~2011-07-29 7:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 13:12 [patch 0/3] A few patches for dcache Cyrill Gorcunov
2011-07-28 13:12 ` [patch 1/3] vfs, dcache: Introduce lighten r/o rename_lock lockers Cyrill Gorcunov
2011-07-28 13:12 ` [patch 2/3] vfs, dcache: Factor out rename_lock locking Cyrill Gorcunov
2011-07-28 13:12 ` [patch 3/3] vfs: Make the rename_lock per-sb Cyrill Gorcunov
2011-07-29 3:25 ` [patch 0/3] A few patches for dcache Dave Chinner
2011-07-29 5:59 ` Cyrill Gorcunov
2011-07-29 6:59 ` Dave Chinner
2011-07-29 7:01 ` Cyrill Gorcunov [this message]
2011-07-29 7:24 ` Al Viro
2011-07-29 7:50 ` Cyrill Gorcunov
2011-08-15 7:42 ` Cyrill Gorcunov
2011-08-24 6:31 ` Pavel Emelyanov
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=20110729070153.GC15883@sun \
--to=gorcunov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=xemul@openvz.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;
as well as URLs for NNTP newsgroup(s).