From: Rich Brown <richb.hanover@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] What is your favourite Flent feature?
Date: Tue, 25 Apr 2017 21:35:19 -0400 [thread overview]
Message-ID: <D4F7D70D-75B3-4764-A04C-9EB97A69FF3D@gmail.com> (raw)
In-Reply-To: <mailman.1.1493136001.28854.bloat@lists.bufferbloat.net>
[-- Attachment #1: Type: text/plain, Size: 422 bytes --]
> On Apr 25, 2017, at 12:00 PM, bloat-request@lists.bufferbloat.net wrote:
>
> What is your favourite Flent feature?
You already know this, but my favorite feature of Flent is that it gives repeatable tests. So much of what I see on various forums that passes for "a test" is likely to be a near-random result. If I knew people were using Flent, I'd be able to ascribe more value to their results.
Best,
Rich
[-- Attachment #2: Type: text/html, Size: 1299 bytes --]
next parent reply other threads:[~2017-04-26 1:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1493136001.28854.bloat@lists.bufferbloat.net>
2017-04-26 1:35 ` Rich Brown [this message]
2017-04-27 11:16 ` Toke Høiland-Jørgensen
2017-04-25 11:49 Toke Høiland-Jørgensen
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=D4F7D70D-75B3-4764-A04C-9EB97A69FF3D@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@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