From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] system responsiveness
Date: Wed, 1 May 2002 15:20:27 -0400 [thread overview]
Message-ID: <20020501192027.14671.qmail@f.bio.cse.psu.edu> (raw)
In-Reply-To: Message from forsyth@caldo.demon.co.uk of "Wed, 01 May 2002 20:13:03 BST." <854ede56869ced0eea759e5201048991@caldo.demon.co.uk>
| i've got a full 4th edition network having upgraded
| my 3rd edition network at home. as i use it, i keep
| thinking it feels somewhat faster than the previous
| release, on precisely the same hardware.
On a similar topic, how is the realtime scheduler working out?
next prev parent reply other threads:[~2002-05-01 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 19:13 forsyth
2002-05-01 19:20 ` Scott Schwartz [this message]
2002-05-02 5:05 ` William Josephson
2002-05-01 19:49 Sape Mullender
2002-05-02 4:42 rob pike, esq.
2002-05-02 5:14 plan9
2002-05-02 5:18 forsyth
2002-05-02 8:29 forsyth
2002-05-02 15:11 Russ Cox
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=20020501192027.14671.qmail@f.bio.cse.psu.edu \
--to=schwartz@bio.cse.psu.edu \
--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).