public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Jackson <jeremy.jackson@sympatico.ca>
To: "Gord R. Lamb" <glamb@lcis.dyndns.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Samba performance / zero-copy network I/O
Date: Wed, 14 Feb 2001 15:42:34 -0500	[thread overview]
Message-ID: <3A8AEDB9.59721801@sympatico.ca> (raw)
In-Reply-To: <Pine.LNX.4.32.0102141452210.27843-100000@localhost.localdomain>

"Gord R. Lamb" wrote:

> Hi everyone,
>
> I'm trying to optimize a box for samba file serving (just contiguous block
> I/O for the moment), and I've now got both CPUs maxxed out with system
> load.
>
> (For background info, the system is a 2x933 Intel, 1gb system memory,
> 133mhz FSB, 1gbit 64bit/66mhz FC card, 2x 1gbit 64/66 etherexpress boards
> in etherchannel bond, running linux-2.4.1+smptimers+zero-copy+lowlatency)
>
> CPU states typically look something like this:
>
> CPU states:  3.6% user,  94.5% system,  0.0% nice, 1.9% idle
>
> .. with the 3 smbd processes each drawing around 50-75% (according to
> top).
>
> When reading the profiler results, the largest consuming kernel (calls?)
> are file_read_actor and csum_partial_copy_generic, by a longshot (about
> 70% and 20% respectively).
>
> Presumably, the csum_partial_copy_generic should be eliminated (or at
> least reduced) by David Miller's zerocopy patch, right?  Or am I
> misunderstanding this completely? :)

I only know enough to be dangerous here, but I believe you will need to
be using one of the network cards whose driver actually uses the
zero-copy patches, and/or which can perform tcp checksum in hardware
(of the network card).


  parent reply	other threads:[~2001-02-14 20:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14 20:14 Samba performance / zero-copy network I/O Gord R. Lamb
2001-02-14 20:29 ` Alan Cox
2001-02-14 20:42 ` Jeremy Jackson [this message]
2001-02-14 20:53   ` Gord R. Lamb
2001-02-14 22:40     ` Tom Sightler
2001-02-16  2:24       ` Gord R. Lamb
2001-02-16 14:51       ` Andrew Morton
2001-02-16 20:49         ` Tom Sightler
2001-02-17  8:17     ` Anton Blanchard
2001-02-19 16:47       ` Gord R. Lamb

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=3A8AEDB9.59721801@sympatico.ca \
    --to=jeremy.jackson@sympatico.ca \
    --cc=glamb@lcis.dyndns.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox