From: Wendy Cheng <wcheng@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 Patch] pass formal ino in do_filldir_main
Date: Tue, 27 Feb 2007 15:04:25 -0500 [thread overview]
Message-ID: <45E48EC9.3020408@redhat.com> (raw)
In-Reply-To: <1172510168.3246.16.camel@localhost.localdomain>
Steven Whitehouse wrote:
> In the mean time no_formal_ino will still exist, its just that it won't
> be used as the lookup key, so theres no on-disk format change to
> consider here, all the same fields will continue to have the same
> values, so there should be no problem to use it again if required at a
> later date,
>
>
ok, as long as we don't rush into removing the code, this is an
acceptable plan. We can discuss the issue further when we meet
face-to-face next month. In the mean time, will go ahead to make lookup
code consistent by tentatively putting no_formal_ino aside. Without the
changes, half of the current NFS lookups would fail. We need to have
something working right now.
I also invite Kent Baxley (one of our TAMs) here to help out with the
issue. I recalled he mentioned sometime ago that the "create" table in
GFS2-mySQL benchmark was noticeably slow - not sure whether
pick_formal_ino() plays any role there. Will give him two gfs2.ko to
re-run the benchmark and see what we get.
-- Wendy
next prev parent reply other threads:[~2007-02-27 20:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 4:51 [Cluster-devel] [GFS2 Patch] pass formal ino in do_filldir_main Wendy Cheng
2007-02-07 10:49 ` Steven Whitehouse
2007-02-07 22:35 ` Wendy Cheng
2007-02-07 23:37 ` Wendy Cheng
2007-02-08 9:42 ` Steven Whitehouse
2007-02-24 3:56 ` Wendy Cheng
2007-02-26 15:45 ` Steven Whitehouse
2007-02-26 16:11 ` Jonathan E Brassow
2007-02-26 17:16 ` Steven Whitehouse
2007-02-27 20:04 ` Wendy Cheng [this message]
2007-02-28 9:03 ` Steven Whitehouse
2007-02-28 16:24 ` Wendy Cheng
2007-02-28 16:26 ` Wendy Cheng
2007-02-28 16:46 ` Steven Whitehouse
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=45E48EC9.3020408@redhat.com \
--to=wcheng@redhat.com \
/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.