From: "Andrew M. Theurer" <atheurer@austin.ibm.com>
To: Mike Kravetz <mkravetz@sequent.com>
Cc: lse-tech@lists.sourceforge.net,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
samba-technical <samba-technical@samba.org>
Subject: Re: Linux 2.4 Scalability, Samba, and Netbench
Date: Wed, 09 May 2001 12:30:35 -0500 [thread overview]
Message-ID: <3AF97EBB.9F0ABE9A@austin.ibm.com> (raw)
In-Reply-To: <3AF97062.42465A53@austin.ibm.com> <20010509095658.B1150@w-mikek2.sequent.com>
I do have kernprof ACG and lockmeter for a 4P run. We saw no
significant problems with lockmeter. csum_partial_copy_generic was the
highest % in profile, at 4.34%. I'll see if we can get some space on
http://lse.sourceforge.net to post the test data.
Andrew Theurer
Mike Kravetz wrote:
>
> On Wed, May 09, 2001 at 11:29:22AM -0500, Andrew M. Theurer wrote:
> >
> > I am evaluating Linux 2.4 SMP scalability, using Netbench(r) as a
> > workload with Samba, and I wanted to get some feedback on results so
> > far.
>
> Do you have any kernel profile or lock contention data?
>
> --
> Mike Kravetz mkravetz@sequent.com
> IBM Linux Technology Center
next prev parent reply other threads:[~2001-05-09 17:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 16:29 Linux 2.4 Scalability, Samba, and Netbench Andrew M. Theurer
2001-05-09 16:56 ` Mike Kravetz
2001-05-09 17:30 ` Andrew M. Theurer [this message]
2001-05-09 17:35 ` [Lse-tech] " Christoph Hellwig
2001-05-09 17:39 ` Alan Cox
2001-05-09 17:43 ` Andrew M. Theurer
2001-05-09 23:35 ` Chris Evans
2001-05-10 4:51 ` [Lse-tech] " Maneesh Soni
2001-05-10 8:40 ` Dipankar Sarma
2001-05-11 15:20 ` David Collier-Brown
2001-05-10 1:23 ` Kenichi Okuyama
-- strict thread matches above, loose matches on Subject: below --
2001-05-09 23:34 Bruce Allan
2001-05-10 13:38 ` Andrew M. Theurer
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=3AF97EBB.9F0ABE9A@austin.ibm.com \
--to=atheurer@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mkravetz@sequent.com \
--cc=samba-technical@samba.org \
/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.