mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: netdev@oss.sgi.com
Subject: [UPDATE] zerocopy + powder rule
Date: Mon, 12 Feb 2001 23:13:14 -0800 (PST)	[thread overview]
Message-ID: <14984.56970.908321.405130@pizda.ninka.net> (raw)


The only change is to update things to 2.4.2-pre3:

ftp://ftp.kernel.org/pub/linux/kernel/people/davem/zerocopy-2.4.2p3-1.diff.gz

All the reports I am getting now appear to be consistent,
and they all basically show me that:

1) There are no known bugs (as in things that crash the
   kernel or corrupt data)

2) The loopback etc. raw performance anomalies have been
   killed by the P-II Mendocino unaligned memcpy workaround.

3) The acenic/gbit performance anomalies have been cured
   by reverting the PCI mem_inval tweaks.

4) The zerocopy patches have a small yet non-neglible
   cpu usage cost for normal write/send/sendmsg.

If this truly is the current state of affairs, then I am
pretty happy as this is where I wanted things to be when
I first began to publish these zerocopy diffs.  The next
step is to begin profiling things heavily to see if we
can back some of that extra cpu usage the pages SKBs
afford us.

Due to the powder rule (Lake Tahoe received 6 or so feet of snow this
past weekend) I will be a bit quiet until Friday night.  However, I'll
be doing my own profiling of the zerocopy stuff on my laptop while I'm
up there.

Later,
David Snowboard Miller
davem@redhat.com


                 reply	other threads:[~2001-02-13  7:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=14984.56970.908321.405130@pizda.ninka.net \
    --to=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

all inboxes | Powered by JetHome®