From: Dave Taht <dave@taht.net>
To: Aaron Wood <woody77@gmail.com>
Cc: Bruce Ferrell <bferrell@baywinds.org>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] openvswitch usage in the wild?
Date: Fri, 07 Jun 2019 18:27:34 -0700 [thread overview]
Message-ID: <87d0josw6x.fsf@taht.net> (raw)
In-Reply-To: <CALQXh-MCsYwc20L3XqE18iEzKwhLq2MtqmSDnYJR51onVFoE1g@mail.gmail.com> (Aaron Wood's message of "Fri, 7 Jun 2019 18:02:18 -0700")
Aaron Wood <woody77@gmail.com> writes:
> I also know of commercial product(s) using it internally.
Well, the followon question was, do people use the sfq and/or fq_codel
related code in it?
>
> On Fri, Jun 7, 2019 at 4:03 PM Bruce Ferrell <bferrell@baywinds.org>
> wrote:
>
> On 6/7/19 1:23 PM, Dave Taht wrote:
> > what is openvswitch used for nowadays?
> >
> >
> https://mail.openvswitch.org/pipermail/ovs-dev/2015-March/296317.html
>
> >
> I haven't done it myself (it IS on my agenda to try in my copious
> spare time), but I hear tell you can use it to make virtualbox and
> KVM behave like VMWare VCenter using virtual
> interfaces on guest VMs
>
> I also know of commercial product that has (or had, I haven't
> looked lately) it baked in (no, I'm not at liberty to mention
> which one).
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2019-06-08 1:27 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 [this message]
2019-06-09 11:46 ` Simon Leinen
2019-06-14 21:04 ` Dave Taht
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=87d0josw6x.fsf@taht.net \
--to=dave@taht.net \
--cc=bferrell@baywinds.org \
--cc=bloat@lists.bufferbloat.net \
--cc=woody77@gmail.com \
/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