From: tao.ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 0/3] Add inode stealing for ocfs2.V1
Date: Fri Feb 22 01:03:36 2008 [thread overview]
Message-ID: <47BE8FE1.4070901@oracle.com> (raw)
In-Reply-To: <47BE89FE.1090204@oracle.com>
wengang wang wrote:
> not know it clearly, but I remember when extending a file, meta is
> allocated in extent_alloc instead of inode_alloc if necessary(correct me
> if i am wrong).
yes, extending a file using extent_alloc. But I'm stealing inode not
extent block. So don't need to touch extent_alloc.
> if so, do we need to take extent_alloc into consideration as well?
This solution is just for inodes, not extents.
>
> thanks,
> wengang.
>
next prev parent reply other threads:[~2008-02-22 1:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 0:42 [Ocfs2-devel] [PATCH 0/3] Add inode stealing for ocfs2.V1 Tao Ma
2008-02-22 0:48 ` [Ocfs2-devel] [PATCH 1/3] Add a new parameter for ocfs2_reserve_suballoc_bits.V1 Tao Ma
2008-02-22 0:49 ` [Ocfs2-devel] [PATCH 2/3] Add ac_alloc_slot in ocfs2_alloc_context.V1 Tao Ma
2008-02-22 0:49 ` [Ocfs2-devel] [PATCH 3/3] Add inode stealing for ocfs2_reserve_new_inode.V1 Tao Ma
2008-02-22 0:57 ` [Ocfs2-devel] [PATCH 0/3] Add inode stealing for ocfs2.V1 wengang wang
2008-02-22 1:03 ` tao.ma [this message]
2008-02-22 1:17 ` wengang wang
2008-02-22 1:26 ` tao.ma
2008-02-22 10:30 ` Sunil Mushran
2008-02-22 15:09 ` Mark Fasheh
2008-02-22 16:11 ` Tao Ma
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=47BE8FE1.4070901@oracle.com \
--to=tao.ma@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.