From: Dave Chinner <david@fromorbit.com>
To: Waiman Long <Waiman.Long@hp.com>
Cc: linux-fsdevel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] dcache: make Oracle more scalable on large systems
Date: Fri, 22 Feb 2013 10:38:18 +1100 [thread overview]
Message-ID: <20130221233818.GM26694@dastard> (raw)
In-Reply-To: <1361299859-27056-1-git-send-email-Waiman.Long@hp.com>
On Tue, Feb 19, 2013 at 01:50:55PM -0500, Waiman Long wrote:
> It was found that the Oracle database software issues a lot of call
> to the seq_path() kernel function which translates a (dentry, mnt)
> pair to an absolute path. The seq_path() function will eventually
> take the following two locks:
Nobody should be doing reverse dentry-to-name lookups in a quantity
sufficient for it to become a performance limiting factor. What is
the Oracle DB actually using this path for?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2013-02-21 23:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 18:50 [PATCH 0/4] dcache: make Oracle more scalable on large systems Waiman Long
2013-02-19 18:50 ` [PATCH 1/4] dcache: Don't take unncessary lock in d_count update Waiman Long
2013-02-19 18:50 ` [PATCH 2/4] dcache: introduce a new sequence read/write lock type Waiman Long
2013-02-19 18:50 ` [PATCH 3/4] dcache: change rename_lock to a sequence read/write lock Waiman Long
2013-02-19 18:50 ` Waiman Long
2013-02-19 18:50 ` [PATCH 4/4] dcache: don't need to take d_lock in prepend_path() Waiman Long
2013-02-21 23:38 ` Dave Chinner [this message]
2013-02-22 0:13 ` [PATCH 0/4] dcache: make Oracle more scalable on large systems Andi Kleen
2013-02-22 4:13 ` Waiman Long
2013-02-22 23:00 ` Dave Chinner
2013-02-23 0:13 ` Andi Kleen
2013-02-28 20:39 ` Waiman Long
2013-02-28 23:13 ` Waiman Long
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=20130221233818.GM26694@dastard \
--to=david@fromorbit.com \
--cc=Waiman.Long@hp.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 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).