From: erik quanstrom <quanstro@quanstro.net>
To: jyu@cowsay.org, 9fans@9fans.net
Subject: Re: [9fans] nix scheduler changes
Date: Tue, 27 May 2014 15:02:59 -0400 [thread overview]
Message-ID: <7067ac627950e9421810328770122e0b@ladd.quanstro.net> (raw)
In-Reply-To: <CACebkGNqEiGXqAornUx7aXTW3WARoSU-yqBTuA2gkpsHhg0C7A@mail.gmail.com>
> Nice. Excited to see how a cleaned up + simplified runproc() and the
> per-Mach queues could also change things. Any reason why the ping test
> w/ monmwait wasn't consistent with the performance improvement in
> other areas?
yes there is. in a later post i describe it, but basically what i saw is that letting
one thread (mach0) get ahead of the others got performance back. but it does
cost power. i have a few ideas i am going to try when i get done with the work
i have scheduled for today.
- erik
prev parent reply other threads:[~2014-05-27 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 17:14 erik quanstrom
2014-05-27 18:15 ` Jessica Yu
2014-05-27 19:02 ` erik quanstrom [this message]
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=7067ac627950e9421810328770122e0b@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=jyu@cowsay.org \
/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).