From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: lm@gate1-neteng.engr.sgi.com (Larry McVoy)
Cc: davem@caip.rutgers.edu, lmlinux@neteng.engr.sgi.com,
torvalds@cs.Helsinki.FI, sparclinux-cvs@caipfs.rutgers.edu,
alan@cymru.net
Subject: Re: lmbench with new checksum code...
Date: Thu, 16 May 1996 18:32:51 +0100 (BST) [thread overview]
Message-ID: <m0uK6ux-0005FbC@lightning.swansea.linux.org.uk> (raw)
In-Reply-To: <199605161603.JAA03193@neteng.engr.sgi.com> from "Larry McVoy" at May 16, 96 09:03:36 am
> I think your 4.8MB/sec number is pretty studly. That means you are
> checksumming 9MB/sec as well as the protocol stack on a system that
Actually the Linux kernel cheats on the receive side of loopback and doesnt
checksum. Its too expensive to fiddle around on the send side for that short
of doing the whole job and shorting the tcp layer as Solaris seems to.
> bcopies at ~20MB/sec. You're already better than 2x the SunOS code.
> Call it a day, you won.
Na.. We can cut all the checksums, do raw copies with no protocol overhead
and possibly later on do user->user copying (with page flips to keep larry
happy ;)). I can't see any reason we cannot do about 8-9MB/sec with a bit
of extra code and some sneaky tricks.
CONFIG_TCP_BENCHMARK_TRICKS
anyone ?
WARNING: multiple messages have this Message-ID (diff)
From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: Larry McVoy <lm@gate1-neteng.engr.sgi.com>
Cc: davem@caip.rutgers.edu, lmlinux@neteng.engr.sgi.com,
torvalds@cs.Helsinki.FI, sparclinux-cvs@caipfs.rutgers.edu,
alan@cymru.net
Subject: Re: lmbench with new checksum code...
Date: Thu, 16 May 1996 18:32:51 +0100 (BST) [thread overview]
Message-ID: <m0uK6ux-0005FbC@lightning.swansea.linux.org.uk> (raw)
Message-ID: <19960516173251.FGnw41PaVnl8S_jLdTfCnG0oy7dvMTNLQe5evwafm_k@z> (raw)
In-Reply-To: <199605161603.JAA03193@neteng.engr.sgi.com> from "Larry McVoy" at May 16, 96 09:03:36 am
> I think your 4.8MB/sec number is pretty studly. That means you are
> checksumming 9MB/sec as well as the protocol stack on a system that
Actually the Linux kernel cheats on the receive side of loopback and doesnt
checksum. Its too expensive to fiddle around on the send side for that short
of doing the whole job and shorting the tcp layer as Solaris seems to.
> bcopies at ~20MB/sec. You're already better than 2x the SunOS code.
> Call it a day, you won.
Na.. We can cut all the checksums, do raw copies with no protocol overhead
and possibly later on do user->user copying (with page flips to keep larry
happy ;)). I can't see any reason we cannot do about 8-9MB/sec with a bit
of extra code and some sneaky tricks.
CONFIG_TCP_BENCHMARK_TRICKS
anyone ?
next prev parent reply other threads:[~1996-05-16 22:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-16 16:03 lmbench with new checksum code Larry McVoy
1996-05-16 17:32 ` Alan Cox [this message]
1996-05-16 17:32 ` Alan Cox
1996-05-17 4:01 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
1996-05-16 19:03 Neal Nuckolls
1996-05-16 6:53 David S. Miller
1996-05-16 9:35 ` Alan Cox
1996-05-16 9:35 ` Alan Cox
1996-05-16 10:08 ` Linus Torvalds
1996-05-16 16:03 ` Greg Chesson
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=m0uK6ux-0005FbC@lightning.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=alan@cymru.net \
--cc=davem@caip.rutgers.edu \
--cc=lm@gate1-neteng.engr.sgi.com \
--cc=lmlinux@neteng.engr.sgi.com \
--cc=sparclinux-cvs@caipfs.rutgers.edu \
--cc=torvalds@cs.Helsinki.FI \
/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.