All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Reoganize data elements to reduce memory footprint
Date: Wed, 9 Jun 2010 17:54:49 -0700	[thread overview]
Message-ID: <20100610005448.GC27385@mail.oracle.com> (raw)
In-Reply-To: <20100610004509.GA27385@mail.oracle.com>

On Wed, Jun 09, 2010 at 05:45:10PM -0700, Joel Becker wrote:
> > diff --git a/fs/ocfs2/ocfs2.h b/fs/ocfs2/ocfs2.h
> > index c67003b..34b9c79 100644
> > --- a/fs/ocfs2/ocfs2.h
> > +++ b/fs/ocfs2/ocfs2.h
> > @@ -151,17 +151,16 @@ struct ocfs2_lock_res {
> >  	void                    *l_priv;
> >  	struct ocfs2_lock_res_ops *l_ops;
> >  	spinlock_t               l_lock;
> > +	enum ocfs2_lock_type     l_type;

	On the subject of extreme structure diets...  ocfs2_lock_res
uses ints for l_ro_holders and l_ex_holders.  Do we ever have more than
64K holders?  Can we squash those into u16s?  I note that our code
doesn't handle overflow at all, but 2^32 holders is significantly
larger.
	Goldwyn, did you test this with CONFIG_OCFS2_FS_STATS and
CONFIG_DEBUG_LOCK_ENABLED turned on or off?  I'd be interested in that
data too.

Joel

-- 

"But all my words come back to me
 In shades of mediocrity.
 Like emptiness in harmony
 I need someone to comfort me."

Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127

  parent reply	other threads:[~2010-06-10  0:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 21:57 [Ocfs2-devel] [PATCH] Reoganize data elements to reduce memory footprint Goldwyn Rodrigues
2010-06-09 23:46 ` Sunil Mushran
2010-06-10  0:45 ` Joel Becker
2010-06-10  0:51   ` Joel Becker
2010-06-10  0:54   ` Joel Becker [this message]
2010-06-10  4:07     ` Goldwyn Rodrigues
2010-06-10  0:56   ` 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=20100610005448.GC27385@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.