From: Wes Felter <wmf@felter.org>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] bulk packet transmission
Date: Wed, 15 Oct 2014 14:49:35 -0500 [thread overview]
Message-ID: <m1mj4f$63b$1@ger.gmane.org> (raw)
In-Reply-To: <1412988767.10122173@apps.rackspace.com>
On 10/10/14, 7:52 PM, dpreed@reed.com wrote:
> The best approach to dealing with "locking overhead" is to stop thinking
> that if locks are good, more locking (finer grained locking) is better.
> OS designers (and Linux designers in particular) are still putting in
> way too much locking. I deal with this in my day job (we support
> systems with very large numbers of cpus and because of the "fine
> grained" locking obsession, the parallelized capacity is limited). If
> you do a thoughtful design of your network code, you don't need lots of
> locking - because TCP/IP streams don't have to interact much - they are
> quite independent. But instead OS designers spend all their time
> thinking about doing "one thing at a time".
The IX project looks like a promising step in that direction, although
it still doesn't support sub-core granularity like Linux does.
https://www.usenix.org/conference/osdi14/technical-sessions/presentation/belay
--
Wes Felter
IBM Research - Austin
next prev parent reply other threads:[~2014-10-15 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 19:40 David Lang
2014-10-09 19:48 ` Dave Taht
2014-10-11 0:52 ` dpreed
2014-10-11 3:15 ` David Lang
2014-10-11 4:20 ` David P. Reed
2014-10-13 22:11 ` Dave Taht
2014-10-15 19:49 ` Wes Felter [this message]
2014-10-15 22:41 ` dpreed
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='m1mj4f$63b$1@ger.gmane.org' \
--to=wmf@felter.org \
--cc=cerowrt-devel@lists.bufferbloat.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