From: Kathleen Nichols <nichols@pollere.com>
To: codel@lists.bufferbloat.net
Subject: Re: [Codel] ns2 simulations of sfq_codel
Date: Sun, 13 Jan 2013 20:15:37 -0800 [thread overview]
Message-ID: <50F38669.3010600@pollere.com> (raw)
In-Reply-To: <CAMdC6xbF6n=GTnGiLCf7O3zPV65bX-QLVCkXB=2MSWn8YQ0QfQ@mail.gmail.com>
Sounds like you didn't add the variables to tcl/libns-default.tcl
On 1/13/13 7:57 PM, Anirudh Sivaraman wrote:
> Hi
>
> I am using ns2 to simulate sfq_codel (code taken from
> https://github.com/dtaht/ns2/blob/master/queue/sfqcodel.cc). I
> modified codel.tcl
> (https://github.com/dtaht/ns2/blob/master/codel.tcl) to run sfq_codel.
> Specifically, I modified this line in codel.tcl :
>
> $ns duplex-link $n0 $n1 $bw ${bdelay}ms CoDel
>
> to
>
> $ns duplex-link $n0 $n1 $bw ${bdelay}ms sfqCoDel
>
> Things run fine, except I get these warnings :
>
> warning: no class variable Queue/sfqCoDel::interval_
>
> see tcl-object.tcl in tclcl for info about this warning.
>
> warning: no class variable Queue/sfqCoDel::target_
>
> warning: no class variable Queue/sfqCoDel::curq_
>
> warning: no class variable Queue/sfqCoDel::d_exp_
>
> warning: no class variable Queue/sfqCoDel::interval_
>
> see tcl-object.tcl in tclcl for info about this warning.
>
> warning: no class variable Queue/sfqCoDel::target_
>
> warning: no class variable Queue/sfqCoDel::curq_
>
> warning: no class variable Queue/sfqCoDel::d_exp_
>
> Are these warnings safe to ignore or do they affect the simulation output ?
>
> Anirudh
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
>
next prev parent reply other threads:[~2013-01-14 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 3:57 Anirudh Sivaraman
2013-01-14 4:15 ` Kathleen Nichols [this message]
2013-01-14 4:28 ` Anirudh Sivaraman
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=50F38669.3010600@pollere.com \
--to=nichols@pollere.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