From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] [Ecn-sane] containers and network namespaces
Date: Tue, 28 May 2019 09:13:07 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1905280911350.2454@uplift.swm.pp.se> (raw)
In-Reply-To: <CAA93jw7iaZQ0zqCaQsXyuXsNc97BOeFVBsr9Vp8ZLJjR7SpHFg@mail.gmail.com>
On Mon, 27 May 2019, Dave Taht wrote:
> clear to me, either, how often network namespaces are used in the
> field(?) out of that billions deployment, but here a few months back,
> I had showed the issues network namespaces had (at that point in time)
> with self-congesting on overload:
I was under the impression that basically all containers used network
namespaces to do whatever it is they do. All (most) the guides I have seen
on how to setup container networking seems to propose configuration setups
where namespaces are used.
--
Mikael Abrahamsson email: swmike@swm.pp.se
prev parent reply other threads:[~2019-05-28 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 15:21 [Bloat] " Dave Taht
2019-05-28 7:13 ` Mikael Abrahamsson [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=alpine.DEB.2.20.1905280911350.2454@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=ecn-sane@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