From: Sebastian Moeller <moeller0@gmx.de>
To: Michael Menth <menth@uni-tuebingen.de>
Cc: "Dave Täht" <dave.taht@gmail.com>,
bloat <bloat@lists.bufferbloat.net>,
codel@lists.bufferbloat.net
Subject: Re: [Codel] [Bloat] Another passive bandwidth estimation method
Date: Tue, 1 Aug 2023 09:51:37 +0200 [thread overview]
Message-ID: <7FD3B872-7B3E-43E2-BC82-172E50C2C22C@gmx.de> (raw)
In-Reply-To: <507f856e-486c-87ff-79a3-50eb47683557@uni-tuebingen.de>
Hi Michael,
that "teaser" you wrote is certainly interesting. Would you be able to distribute author copies to those of us that do not subscribe to IEEExplore, please?
Regards
Sebastian
> On Aug 1, 2023, at 09:32, Michael Menth via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> Hi all,
>
> we've recently developed a passive method for finding a link's capacity (in a different context). You find the algorithm in III.B.5 in
> https://ieeexplore.ieee.org/document/9954450
> The approach ist tested in V.B for 1, 10, and 100 Gb/s links on a Linux server and provides sufficiently accurate results for bandwidth utilizations of 25%. The method is likely to work also for lower utilizations, but this was not an issue in this work. The method is applicable only by a link's head-end node. It does not work for end systems to find the bottleneck bandwidth on some unknown intermediate node. However, it can deliver useful information for scheduling algorithms in forwarding nodes, which is the use case in this paper, and which may be of interest to some readers on this list.
>
> Kind regards
>
> Michael
>
>
> Am 01.08.2023 um 00:36 schrieb Dave Taht via Bloat:
>> Promising approach:
>>
>> https://ieeexplore.ieee.org/document/10188775
>
> --
> Prof. Dr. habil. Michael Menth
> University of Tuebingen
> Faculty of Science
> Department of Computer Science
> Chair of Communication Networks
> Sand 13, 72076 Tuebingen, Germany
> phone: (+49)-7071/29-70505
> fax: (+49)-7071/29-5220
> mailto:menth@uni-tuebingen.de
> http://kn.inf.uni-tuebingen.de
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2023-08-01 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 22:36 [Codel] slow start: small chunks can talk Dave Taht
[not found] ` <507f856e-486c-87ff-79a3-50eb47683557@uni-tuebingen.de>
2023-08-01 7:51 ` Sebastian Moeller [this message]
[not found] ` <4a158f4f-4f96-44bf-8b08-6f84b0d660df@uni-tuebingen.de>
2023-08-01 8:37 ` [Codel] [Bloat] Another passive bandwidth estimation method Dave Taht
[not found] ` <6392cb1d-92e5-f289-c684-5850bf87df4a@kit.edu>
2023-08-07 10:18 ` [Codel] [Bloat] slow start: small chunks can talk Sebastian Moeller
2023-08-07 16:34 ` 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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7FD3B872-7B3E-43E2-BC82-172E50C2C22C@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=menth@uni-tuebingen.de \
/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