public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Malcolm Beattie <mbeattie@sable.ox.ac.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [UPDATE] Fresh zerocopy patch on kernel.org
Date: Thu, 1 Feb 2001 11:20:15 +0000	[thread overview]
Message-ID: <20010201112014.A27009@sable.ox.ac.uk> (raw)
In-Reply-To: <14966.35438.429963.405587@pizda.ninka.net> <20010131152653.C13345@sable.ox.ac.uk> <14968.49462.674977.825098@pizda.ninka.net>
In-Reply-To: <14968.49462.674977.825098@pizda.ninka.net>; from davem@redhat.com on Wed, Jan 31, 2001 at 05:51:50PM -0800

David S. Miller writes:
> 
> Malcolm Beattie writes:
>  > David S. Miller writes:
>  > > 
>  > > At the usual place:
>  > > 
>  > > ftp://ftp.kernel.org/pub/linux/kernel/people/davem/zerocopy-2.4.1-1.diff.gz
>  > 
>  > Hmm, disappointing results here; maybe I've missed something.
> 
> As discussed elsewhere there is a %10 to %15 performance hit for
> normal write()'s done with the new code.
> 
> If you do your testing using sendfile() as the data source, you'll
> results ought to be wildly different and more encouraging.

I did say that the ftp test used sendfile() as the data source and
it dropped from 86 MB/s to 62 MB/s. Alexey has mailed me suggesting
the problem may be that netfilter is turned on. It is indeed turned
on in both the 2.4.1 config and the 2.4.1+zc config but maybe it has
a far higher detrimental effect in the zerocopy case. I'm currently
building new non-netfilter kernels and I'll go through the exercise
again. I'm confident I'll end up being impressed with the numbers
even if it takes some tweaking to get there :-)

--Malcolm

-- 
Malcolm Beattie <mbeattie@sable.ox.ac.uk>
Unix Systems Programmer
Oxford University Computing Services
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-02-01 11:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30  9:33 [UPDATE] Fresh zerocopy patch on kernel.org David S. Miller
2001-01-30 11:16 ` Chris Wedgwood
2001-01-30 12:23   ` David S. Miller
2001-01-30 18:59 ` Tom Rini
2001-01-31 15:26 ` Malcolm Beattie
2001-02-01  1:51   ` David S. Miller
2001-02-01 11:20     ` Malcolm Beattie [this message]
2001-02-01 11:25       ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2001-01-30 15:58 Pau Aliagas
2001-02-01  8:20 ` Chris Wedgwood
2001-02-01 16:06 Jonathan Earle

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=20010201112014.A27009@sable.ox.ac.uk \
    --to=mbeattie@sable.ox.ac.uk \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.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