From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] cfs
Date: Wed, 13 May 2009 08:34:10 -0400 [thread overview]
Message-ID: <c918e745af7a330e87ad6ac29d1cffc6@quanstro.net> (raw)
In-Reply-To: <816fc530f45f9acd7946837e73cef773@quintile.net>
> Why is cfs in the kernel and not a userlevel program?
i don't know. but by putting cfs in the kernel, you can use the kernel's
built-in concurrency. cfs predates the thread library.
> I guess there might be performance issues also, though these would
> be swamped by the performance improvment of plugging in CFS in the
> first place (IMHO).
why guess? we can get a good approximation. the difference
is a round trip to user space which has bandwidth and latency
costs. i used dd and ramfs to simulate.
userspace kernel
b/w latency b/w latency
i7 2666 460 MB/s 1680µs 3900 MB/s 118µs
Xeon5000 1859 156 MB/s 1205 868 265
AMD64 2604 be 142 MB/s 2511µs 2600 332
AMD64 2004 135 MB/s 2510 2600 324
if you're limited by 1gbe, the bandwidth would be good
but the latency is spoiled. if you're limited by 10gbe,
the vodka's weak, too.
- erik
next prev parent reply other threads:[~2009-05-13 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 11:20 Steve Simon
2009-05-13 12:34 ` erik quanstrom [this message]
2009-05-13 13:01 Steve Simon
2021-01-19 22:50 Steve Simon
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=c918e745af7a330e87ad6ac29d1cffc6@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).