All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Banks <gnb@sgi.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] 1/3 - RPC metrics support
Date: Fri, 2 Apr 2004 10:10:47 +1000	[thread overview]
Message-ID: <20040402001047.GC9409@sgi.com> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C61130435DE4B@lavender-fe.eng.netapp.com>

On Thu, Apr 01, 2004 at 08:45:40AM -0800, Lever, Charles wrote:
> > The minor dimension of the 2d array of struct 
> > rpc_metrics_totals pointed to by rpc_tally is per-CPU.  To 
> > get correct per-CPU separation you will want to 
> > cacheline-align the per-CPU parts (so that cachelines which 
> > straddle the per-CPU parts don't end up bouncing between 
> > CPUs).  For example, in rpc_alloc_tally(),
> > 
> > size = NR_CPUS * ROUNDUP(ops * sizeof(struct 
> > rpc_metric_totals), L1_CACHE_BYTES);
> > 
> > and change the stride of the tl_totals[] initialisation loop.
> 
> that doesn't work, unfortunately, unless sizeof(struct rpc_tally)
> is also an exact multiple of L1_CACHE_BYTES.  otherwise the whole
> metrics array starts on a non-cache-aligned boundary since these
> are all cut from the same piece of memory.

That's right, you'll need to add ____cacheline_aligned like this:

struct rpc_tally {
} ____cacheline_aligned;

Greg.
-- 
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2004-04-02  0:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-01 16:45 [PATCH] 1/3 - RPC metrics support Lever, Charles
2004-04-02  0:10 ` Greg Banks [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-04  2:35 Lever, Charles
2004-04-04  6:17 ` Greg Banks
2004-04-01 17:05 Lever, Charles
2004-04-02  0:17 ` Greg Banks
2004-04-02  0:36 ` Trond Myklebust
2004-04-02  0:49   ` Greg Banks
2004-04-02  1:41     ` Trond Myklebust
2004-04-02  2:42       ` Greg Banks
2004-04-01 15:15 Lever, Charles
2004-04-01 23:58 ` Greg Banks
2004-04-02  0:34   ` Trond Myklebust
2004-04-02  2:33     ` Greg Banks
2004-03-31 16:57 Lever, Charles
2004-03-31 17:19 ` Trond Myklebust
2004-03-31 16:34 Lever, Charles
2004-03-31 16:46 ` Trond Myklebust
2004-04-01  8:13 ` Greg Banks

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=20040402001047.GC9409@sgi.com \
    --to=gnb@sgi.com \
    --cc=Charles.Lever@netapp.com \
    --cc=nfs@lists.sourceforge.net \
    /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.