General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Dave Täht" <dave@taht.net>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] new "vector packet processing" based effort to speed up networking
Date: Fri, 12 Feb 2016 09:40:37 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.02.1602120933550.11524@uplift.swm.pp.se> (raw)
In-Reply-To: <56BCDB72.1000702@taht.net>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1184 bytes --]

On Thu, 11 Feb 2016, Dave Täht wrote:

> Someone asked me recently what I thought of the dpdk. I said:
> "It's a great way to heat datacenters". Still, there's momentum it
> seems, to move more stuff into userspace.

Especially now that Intel CPUs seem to be able to push a lot of PPS 
compared to what they could before. A lot more.

What one has to take into account is that this tech is most likely going 
to be deployed on servers with 10GE NICs or even 25/40/100GE, and they are 
most likely going to be connected to a small buffer datacenter switch 
which will do FIFO on extremely small shared buffer memory (we're talking 
small fractions of a millisecond of buffer at 10GE speed), and usually 
lots of these servers will be behind oversubscribed interconnect links 
between switches.

A completely different use case would of course be if someone started to 
create midrange enterprise routers with 1GE/10GE ports using this 
technology, then it would of course make a lot of sense to have proper 
AQM. I have no idea what kind of performance one can expect out of a low 
power Intel CPU that might fit into one of these...

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2016-02-12  8:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11 19:05 Dave Täht
2016-02-12  8:40 ` Mikael Abrahamsson [this message]
2016-02-12 21:09   ` Benjamin Cronce

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/bloat.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.1602120933550.11524@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=bloat@lists.bufferbloat.net \
    --cc=dave@taht.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