From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] GCC3.0 [Was; Webbrowser]
Date: Thu, 6 Feb 2003 13:43:08 -0500 [thread overview]
Message-ID: <36557fae3384ae433109a2cbc5c820fd@plan9.bell-labs.com> (raw)
In-Reply-To: <20030206113325.O535@fbsd.cpsc.ucalgary.ca>
[-- Attachment #1: Type: text/plain, Size: 96 bytes --]
I'll try to reproduce it but I believe that's the bug we fixed. I'll let you know after
I try.
[-- Attachment #2: Type: message/rfc822, Size: 2645 bytes --]
From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] GCC3.0 [Was; Webbrowser]
Date: Thu, 6 Feb 2003 11:35:16 -0700 (MST)
Message-ID: <20030206113325.O535@fbsd.cpsc.ucalgary.ca>
this is the last message on this subject:
https://lists.cse.psu.edu/archives/9fans/2002-May/017658.html
(it doesn't appear on groups.google.com though, I don't know why -- maybe
the pics attached are to blame?)
indeed we were able to measure improvement in speed, but the behaviour was
still strange, yet even stranger when iostats was involved.
andrey
On Thu, 6 Feb 2003, David Presotto wrote:
> I was under the impression that Dong and I had fixed the TCP problems LANL was
> having. Is this incorrect? Could you tell me what's still slow? I really
> do want our IP stack to stay competative. Our next move is to take advantage
> of the hardware checksuming on the gigabit boards since, in our most recent
> testing, we seem to differ from BSD speeds most because of that.
next prev parent reply other threads:[~2003-02-06 18:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 5:28 okamoto
2003-02-06 5:40 ` andrey mirtchovski
2003-02-06 15:15 ` Ronald G. Minnich
2003-02-06 15:39 ` Tharaneedharan Vilwanathan
2003-02-06 15:45 ` Ronald G. Minnich
2003-02-06 16:31 ` rob pike, esq.
2003-02-06 16:36 ` rob pike, esq.
2003-02-06 16:56 ` matt
2003-02-06 17:11 ` Ronald G. Minnich
2003-02-06 17:25 ` Tharaneedharan Vilwanathan
2003-02-06 17:32 ` andrey mirtchovski
2003-02-06 17:44 ` Sam
2003-02-06 18:07 ` Ronald G. Minnich
2003-02-06 18:14 ` David Presotto
2003-02-06 18:17 ` Ronald G. Minnich
2003-02-06 20:36 ` Dean Prichard
2003-02-06 18:35 ` andrey mirtchovski
2003-02-06 18:43 ` David Presotto [this message]
2003-02-06 19:12 ` David Presotto
2003-02-06 19:20 ` Scott Schwartz
2003-02-06 17:06 ` [9fans] Re: Clean Code & Performance Jack Johnson
2003-02-06 17:23 ` [9fans] GCC3.0 [Was; Webbrowser] David Butler
-- strict thread matches above, loose matches on Subject: below --
2003-02-07 1:46 okamoto
2003-02-06 20:13 Keith Nash
2003-02-06 21:29 ` Tharaneedharan Vilwanathan
2003-02-06 21:33 ` Russ Cox
2003-02-06 21:40 ` Jack Johnson
2003-02-07 8:44 ` Richard Miller
2003-02-07 13:51 ` matt
2003-02-07 14:03 ` Boyd Roberts
2003-02-07 0:06 ` Geoff Collyer
2003-02-07 5:32 ` Skip Tavakkolian
2003-02-06 17:50 C H Forsyth
2003-02-06 18:08 ` Ronald G. Minnich
2003-02-06 1:19 [9fans] Webbrowser Russ Cox
2003-02-06 3:00 ` [9fans] GCC3.0 [Was; Webbrowser] andrey mirtchovski
2003-02-06 4:16 ` andrey mirtchovski
2003-02-06 14:24 ` David Presotto
2003-02-06 15:30 ` andrey mirtchovski
2003-02-06 17:32 ` David Presotto
2003-02-06 18:10 ` William K. Josephson
2003-02-06 18:16 ` Ronald G. Minnich
2003-02-06 18:23 ` William K. Josephson
2003-02-06 21:09 ` Ronald G. Minnich
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=36557fae3384ae433109a2cbc5c820fd@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).