From: "andrey mirtchovski" <mirtchovski@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: Re: RE : RE : [9fans] Plan 9 demos for 4+ CPUs?
Date: Thu, 27 Jul 2006 17:12:14 -0600 [thread overview]
Message-ID: <14ec7b180607271612g7909d20euda46a79b32ce8725@mail.gmail.com> (raw)
In-Reply-To: <14ec7b180607271611h4ec23d9co52b8fa77c234118e@mail.gmail.com>
> you are correct, though in this case i believe the load was caused by
> a lot of ethernet traffic, not the file server itself.
>
i mean interrupt load, not system load
next prev parent reply other threads:[~2006-07-27 23:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 22:32 Andrew Hudson
2006-07-27 22:34 ` geoff
2006-07-27 22:46 ` RE : " Frederic Bonfanti
2006-07-27 22:52 ` andrey mirtchovski
2006-07-27 23:05 ` RE : " Frederic Bonfanti
2006-07-27 23:11 ` andrey mirtchovski
2006-07-27 23:12 ` andrey mirtchovski [this message]
2006-07-27 23:21 ` RE : " Frederic Bonfanti
2006-07-27 23:50 ` andrey mirtchovski
2006-07-28 2:16 ` erik quanstrom
2006-07-28 3:14 ` Anthony Sorace
2006-07-28 8:02 ` Charles Forsyth
2006-07-28 11:04 ` erik quanstrom
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=14ec7b180607271612g7909d20euda46a79b32ce8725@mail.gmail.com \
--to=mirtchovski@gmail.com \
--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).