Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: David Lang <david@lang.hm>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] bulk packet transmission
Date: Thu, 9 Oct 2014 12:40:00 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1410091238190.23992@nftneq.ynat.uz> (raw)

lwn.net has an article about a set of new patches that avoid some locking 
overhead by transmitting multiple packets at once.

It doesn't work for things with multiple queues (like fq_codel) in it's current 
iteration, but it sounds like something that should be looked at and watched for 
latency related issues.

http://lwn.net/Articles/615238/

David Lang

             reply	other threads:[~2014-10-09 19:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-09 19:40 David Lang [this message]
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
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=alpine.DEB.2.02.1410091238190.23992@nftneq.ynat.uz \
    --to=david@lang.hm \
    --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