From: Dave Taht <dave@taht.net>
To: Matthias Tafelmeier <matthias.tafelmeier@gmx.net>
Cc: Ken Birman <kpb3@cornell.edu>, Bob Briscoe <ietf@bobbriscoe.net>,
"ken\@cs.cornell.edu" <ken@cs.cornell.edu>,
"bloat\@lists.bufferbloat.net" <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] DETNET
Date: Wed, 15 Nov 2017 12:16:12 -0800 [thread overview]
Message-ID: <87po8j5mcz.fsf@nemesis.taht.net> (raw)
In-Reply-To: <ecfe6b39-79b3-fa8e-8ec3-43f650efabc2@gmx.net> (Matthias Tafelmeier's message of "Wed, 15 Nov 2017 21:09:32 +0100")
Matthias Tafelmeier <matthias.tafelmeier@gmx.net> writes:
> On 11/15/2017 08:45 PM, Ken Birman wrote:
>> I'm missing context. Can someone tell me why I'm being cc'ed on these?
> right, I cced you so I'm liable to clarify.
>
>> Topic seems germane to me (Derecho uses RDMA on RoCE) but I'm unclear what this thread is "about"
>
> I perceived you as a strong kind of advocate for RDMA, at least that's a
> supposition I hold ever since having read your blogs/research around it.
> It was mentioned here in context with other existing or already
> pertaining technologies as to the purpose of improving network
> performance in general - especially for certain domains. Therefore, I
> thought blending/exchanging knowledge or inciting a discussion might be
> profitable for both worlds.
I'm notorious for trying to engage other folk slightly outside our
circle, thx for carrying on the grand tradition. I do admit it can be
quite a lot to get blindsided by!
>
> Originally, this ML is for the Bufferbloat project, but, occassionally
> it does get captivated ...
Well, the overarching goal here is to reduce latencies on everything
(hardware, interconnects, busses, drivers, oses, stacks) to the bare
minimum, on every technology we can reach, and leverage other ideas in
other technologies to do so, whenever possible.
If we had a name for that, other than bufferbloat, I'd switch to it,
because we are way beyond just dealing with excessive buffering after 6+
years of operation.
I will got read up on ken's RDMA stuff.
>
>>> Feel free to tinker your bayes filter if all sounds too alien.<<
next prev parent reply other threads:[~2017-11-15 20:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 13:45 Matthias Tafelmeier
[not found] ` <87shdr0vt6.fsf@nemesis.taht.net>
2017-11-12 14:58 ` Matthias Tafelmeier
2017-11-12 19:58 ` Bob Briscoe
2017-11-13 17:56 ` Matthias Tafelmeier
2017-11-15 19:31 ` Dave Taht
2017-11-15 19:45 ` Ken Birman
2017-11-15 20:09 ` Matthias Tafelmeier
2017-11-15 20:16 ` Dave Taht [this message]
2017-11-15 21:01 ` Ken Birman
2017-11-18 15:56 ` Matthias Tafelmeier
2017-12-11 20:32 ` Toke Høiland-Jørgensen
2017-12-11 20:43 ` Ken Birman
2017-11-18 15:38 ` Matthias Tafelmeier
2017-11-18 15:45 ` Ken Birman
2017-11-19 18:33 ` Dave Taht
2017-11-19 20:24 ` Ken Birman
2017-11-20 17:56 ` [Bloat] *** GMX Spamverdacht *** DETNET Matthias Tafelmeier
2017-11-20 19:04 ` Ken Birman
2017-12-17 12:46 ` Matthias Tafelmeier
2017-12-17 16:06 ` Ken Birman
2017-11-18 17:55 ` [Bloat] DETNET Matthias Tafelmeier
2017-11-18 19:43 ` Ken Birman
2017-11-18 19:47 ` Ken Birman
2017-11-20 18:32 ` Matthias Tafelmeier
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=87po8j5mcz.fsf@nemesis.taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=ietf@bobbriscoe.net \
--cc=ken@cs.cornell.edu \
--cc=kpb3@cornell.edu \
--cc=matthias.tafelmeier@gmx.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