Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Greg Banks <gnb@sgi.com>
Cc: "Talpey, Thomas" <Thomas.Talpey@netapp.com>,
	NeilBrown <neilb@suse.de>,
	Peter Leckie <pleckie@melbourne.sgi.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: [RFC,PATCH 4/14] knfsd: has_wspace per transport
Date: Wed, 23 May 2007 16:11:38 -0400	[thread overview]
Message-ID: <46549FFA.3000409@oracle.com> (raw)
In-Reply-To: <20070523143903.GM14076@sgi.com>

[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]

Greg Banks wrote:
> On Wed, May 23, 2007 at 09:36:55AM -0400, Chuck Lever wrote:
>> Greg Banks wrote:
>>> On Wed, May 23, 2007 at 12:22:44AM -0500, Tom Tucker wrote:
>>>>
>>>> On 5/22/07 9:32 PM, "Greg Banks" <gnb@sgi.com> wrote:
>>>>
>>>>> On Tue, May 22, 2007 at 12:34:23PM -0500, Tom Tucker wrote:
>>>> I need to do a little clean up (e.g. atomic_inc()) and then I'll add them 
>>>> as
>>>> suggested. If there are dissenters, please speak now...
>>> You should be able to get away with just ++.  They're only stats,
>>> it's not like you have logic depending on them being exact.
>> The usual way to do this is to allocate separate stat arrays for each 
>> CPU.  All the per-CPU arrays are summed only when something wants to 
>> display stat totals.
>>
>> That way you can use ++, be fairly sure you will get accurate 
>> statistics, and not have to be concerned about CPU cache effects or lock 
>> contention.
> 
> Here in SGI, home of the multiple-thousand CPU Linux boxes, making
> data structures per-cpu tends to be done...thoughtfully.
> 
> In any case, the remainder of svc_stat gets no such treatment today.

I based the new NFS client stats on what was done by the networking 
layer, which uses the per-CPU pattern.  I was under the impression that 
methodology was preferred for adding new stat keeping.  But I'm aware 
that the existing NFS client and server stat keeping infrastructure uses 
just a simple array for each RPC program/version.

[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 291 bytes --]

begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel/
version:2.1
end:vcard


[-- Attachment #3: Type: text/plain, Size: 286 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

[-- Attachment #4: Type: text/plain, Size: 140 bytes --]

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-05-23 20:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 19:22 [RFC,PATCH 4/14] knfsd: has_wspace per transport Greg Banks
2007-05-16 21:10 ` J. Bruce Fields
2007-05-17  7:12   ` Greg Banks
2007-05-17 10:30     ` Neil Brown
2007-05-17 12:39       ` Talpey, Thomas
2007-05-18  0:30         ` Neil Brown
2007-05-18  4:05       ` Greg Banks
2007-05-18 13:33         ` Tom Tucker
2007-05-18 13:39           ` Tom Tucker
2007-05-22 11:16           ` Greg Banks
2007-05-22 17:34             ` Tom Tucker
2007-05-23  2:32               ` Greg Banks
2007-05-23  5:22                 ` Tom Tucker
2007-05-23  6:41                   ` Greg Banks
2007-05-23 13:36                     ` Chuck Lever
2007-05-23 14:39                       ` Greg Banks
2007-05-23 20:11                         ` Chuck Lever [this message]
2007-05-18 13:44         ` Talpey, Thomas
2007-05-18  6:21       ` Greg Banks
2007-05-18  6:38         ` Neil Brown

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=46549FFA.3000409@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=Thomas.Talpey@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=gnb@sgi.com \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    --cc=pleckie@melbourne.sgi.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