From: Dave Taht <dave@taht.net>
To: Simon Leinen <simon.leinen@switch.ch>
Cc: Dave Taht <dave.taht@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] openvswitch usage in the wild?
Date: Fri, 14 Jun 2019 14:04:38 -0700 [thread overview]
Message-ID: <875zp7lvyx.fsf@taht.net> (raw)
In-Reply-To: <aatvczvv57.fsf@switch.ch> (Simon Leinen's message of "Sun, 9 Jun 2019 13:46:28 +0200")
Simon Leinen <simon.leinen@switch.ch> writes:
> Dave Taht writes:
>> what is openvswitch used for nowadays?
>> https://mail.openvswitch.org/pipermail/ovs-dev/2015-March/296317.html
>
> In OpenStack deployments, "ML2+OVS" is a popular backend for the
> "Neutron" networking service - maybe the most popular for mid-size
> installations.
>
> We and many others use it. However I haven't heard of anyone using sfq
> or fq_codel (or any other fancy qdisc) in this context.
good to have this very broad summary! Thx everyone!
prev parent reply other threads:[~2019-06-14 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 20:23 Dave Taht
2019-06-07 23:03 ` Bruce Ferrell
2019-06-08 1:02 ` Aaron Wood
2019-06-08 1:27 ` Dave Taht
2019-06-09 11:46 ` Simon Leinen
2019-06-14 21:04 ` Dave Taht [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
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=875zp7lvyx.fsf@taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=simon.leinen@switch.ch \
/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