From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add a new code 'OCFS2_INFO_FREEINODE' for o2info ioctl.
Date: Thu, 4 Nov 2010 14:24:36 -0700 [thread overview]
Message-ID: <20101104212436.GE22663@mail.oracle.com> (raw)
In-Reply-To: <4CD26A8A.6080307@oracle.com>
On Thu, Nov 04, 2010 at 04:10:50PM +0800, tristan wrote:
> Yep, you're correct, other than the operation we read inode block,
> the lookup
> of blkno/inode should also be treated differently according to coherency
> flag, I
> guess following logic could help:
>
> if (cluster_coherent) {
> alloc_inode = ocfs2_get_system_file_inode();
> ocfs2_inode_lock(alloc_inode, &bh);
> } else {
> ocfs2_lookup_ino_from_name("global_bitmap", &blkno);
> ocfs2_read_blocks(blkno, 1, &bh);
> }
> ...
>
> Above logic guarantee the performance for none-coherency case.
You got it. But don't hardcode file names. Use the sprintf
function for type+slot as in the top of _ocfs2_get_system_file_inode().
or write a lookup_ino_by_type. Or something like that.
Joel
--
Life's Little Instruction Book #80
"Slow dance"
Joel Becker
Senior Development Manager
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
prev parent reply other threads:[~2010-11-04 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 11:02 [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add a new code 'OCFS2_INFO_FREEINODE' for o2info ioctl Tristan Ye
2010-11-03 11:02 ` [Ocfs2-devel] [PATCH 2/2] Ocfs2: Add a new code 'OCFS2_INFO_FREEFRAG' " Tristan Ye
2010-11-04 1:29 ` Joel Becker
2010-11-04 2:56 ` tristan
2010-11-04 4:47 ` tristan
2010-11-04 6:32 ` Joel Becker
2010-11-04 7:05 ` tristan
2010-12-07 0:46 ` Joel Becker
2010-11-04 1:18 ` [Ocfs2-devel] [PATCH 1/2] Ocfs2: Add a new code 'OCFS2_INFO_FREEINODE' " Joel Becker
2010-11-04 2:27 ` tristan
2010-11-04 6:28 ` Joel Becker
2010-11-04 8:10 ` tristan
2010-11-04 21:24 ` Joel Becker [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=20101104212436.GE22663@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=ocfs2-devel@oss.oracle.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.