From: Nimrod Aviram <nimrod.aviram@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Active Queue Management for applicative layer
Date: Sun, 2 Oct 2011 18:51:03 +0200 [thread overview]
Message-ID: <CABiKAoTK9=59AuG23zBsJhg3R-b6t2xMrM4Wn9wqbqzspYAkUg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
Hi all,
I'm a newbie, so my apologies if I'm directing this question to the wrong
list or anything :-)
I'm writing code for an applicative layer (scsi), transported inside tcp
(which is overall called iScsi).
This applicative layer is very prone to timeouts, specifically anything not
acked (in a scsi way) after 3 seconds is aborted,
which means any bandwidth we already spent on the request was a complete
waste.
I'd like to implement an Active Queue Management scheme, so that latency is
no longer than a second,
and throughput is as high as possible.
Is there any standard code that already does this, or anything similar?
I would really appreciate any pointers you can throw my way, I'm kind of "in
the dark" here.
many thanks,
Nimrod
[-- Attachment #2: Type: text/html, Size: 844 bytes --]
reply other threads:[~2011-10-02 16:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CABiKAoTK9=59AuG23zBsJhg3R-b6t2xMrM4Wn9wqbqzspYAkUg@mail.gmail.com' \
--to=nimrod.aviram@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