From: divya singla <divyasingla1989@gmail.com>
To: codel@lists.bufferbloat.net
Subject: [Codel] About Packet Drop in Codel
Date: Thu, 26 Feb 2015 22:42:32 +0530 [thread overview]
Message-ID: <CAONkte9+XLPomhAkwoN6hwGz6a0BkbBDDQF__mGpRaTvB8XcRA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
Hi Members,
i am doing M.tech and my research topic is AQM.
i tried to run codel with ns-2.35.
And i found packet loss is more in codel as compared to RED.
is there anybody who also thinks the same or is it in my case only?
Am i doing something wrong?
[-- Attachment #2: Type: text/html, Size: 339 bytes --]
next reply other threads:[~2015-02-26 17:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 17:12 divya singla [this message]
2015-02-26 18:32 ` Richard Scheffenegger
2015-02-26 23:14 ` Stephen Hemminger
2015-03-02 17:43 ` divya singla
2015-03-02 18:10 ` Rick Jones
2015-03-02 18:22 ` Jonathan Morton
2015-03-02 18:43 ` divya singla
2015-03-02 19:07 ` Jonathan Morton
2015-03-03 18:12 ` divya singla
2015-03-03 18:27 ` Rick Jones
2015-03-02 18:35 ` Jonathan Morton
[not found] <mailman.153549.1425025588.1815.codel@lists.bufferbloat.net>
2015-02-28 1:57 ` David Collier-Brown
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=CAONkte9+XLPomhAkwoN6hwGz6a0BkbBDDQF__mGpRaTvB8XcRA@mail.gmail.com \
--to=divyasingla1989@gmail.com \
--cc=codel@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