ocfs2-devel.oss.oracle.com archive mirror
 help / color / mirror / Atom feed
From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: Cache some system inodes of other nodes.
Date: Fri, 13 Aug 2010 08:49:16 +0800	[thread overview]
Message-ID: <4C64968C.6030403@oracle.com> (raw)
In-Reply-To: <20100812094350.GB6561@mail.oracle.com>

Joel Becker wrote:
> On Thu, Aug 12, 2010 at 05:03:16PM +0800, Tao Ma wrote:
>   
>> In ocfs2, we now only cache the inodes for global system file
>> and the system inodes for our own slot. But we have some cases
>> that we may need to access system inodes of other nodes, such
>> as orphan scan, inode steal etc.
>>     
>
> 	I don't see why you don't extend the existing cache and make one
> cache.  Make it live the lifetime of the filesystem.  No real reason to
> a) have to caches or b) limit the system inodes we might cache.  If we
> don't have the lock we're going to re-read them anyway.
>   
You want me to do:
-        struct inode *system_inodes[NUM_SYSTEM_INODES];
+        struct inode **system_inodes

and do
+    system_inodes = kzalloc((NUM_SYSTEM_INODES - 
GROUP_QUOTA_SYSTEM_INODE) *
+                                            sizeof(struct inode *) * 
osb->max_slots);

So we will save other system inodes such as local_alloc, truncate_log, 
local_user_quota and local_group_quota and
actually we will never touch these inodes in the most cases(well, 
recovery is an exception). So why cache them
if in the most case they will not be used?
In http://oss.oracle.com/pipermail/ocfs2-devel/2010-June/006562.html, 
Goldwyn try to reduce our size by just
moving the postion of some fields, so I think we should save these 
memory for the kernel. :)

Regards,
Tao

  reply	other threads:[~2010-08-13  0:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12  9:03 [Ocfs2-devel] [PATCH] ocfs2: Cache some system inodes of other nodes Tao Ma
2010-08-12  9:43 ` Joel Becker
2010-08-13  0:49   ` Tao Ma [this message]
2010-08-13  1:04     ` Joel Becker
2010-08-13  1:20       ` Tao Ma
2010-08-13  1:03   ` Sunil Mushran
2010-08-13  1:21     ` Tao Ma
2010-08-13  1:28       ` Joel Becker

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=4C64968C.6030403@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 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).