CoDel AQM discussions
 help / color / mirror / Atom feed
From: sahil grover <sahilgrover013@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] RRUL Test
Date: Fri, 17 Apr 2015 20:22:20 +0530	[thread overview]
Message-ID: <CADnS-2g+OneXB1aapFe68hhZyDeAwJ9tLD1_ZnBOysCnC3ni4w@mail.gmail.com> (raw)
In-Reply-To: <87sibz53kz.fsf@toke.dk>

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

Thanks Andrew Sir and Toke Sir for replying.

Toke Sir,

Please clear one more thing.

According to  Quick Start(
https://github.com/tohojo/netperf-wrapper#quick-start):
#### You must install netperf on two computers.Netperf needs to be started
in “server mode” on one #computer so it can listen for commands from the
other.

####Note: You may also use the netserver that is running on
netperf.bufferbloat.net - use “-H #netperf.bufferbloat.net” in the commands
above.


if i choose  "netperf.bufferbloat.net" as a server then i think i can
proceed with one computer for bufferbloat test.
Does it make any difference?
i just need your confirmation.



On Fri, Apr 17, 2015 at 6:12 PM, Toke Høiland-Jørgensen <toke@toke.dk>
wrote:

> sahil grover <sahilgrover013@gmail.com> writes:
>
> > will ubuntu 12.04 be ok?
> >
> > can you please tell me step by step installation of RRUL(or
> > netperf-wrapper)?
>
> There's an ubuntu 12.04 repository with netperf-wrapper and the required
> version of netperf at the open build service repository. See:
>
>
> https://software.opensuse.org/download.html?project=home:tohojo:netperf-wrapper&package=netperf-wrapper
>
> That link contains instructions for how to enable the repository on
> Ubuntu and install the netperf-wrapper package.
>
> As far as running it, have a look at the Quick Start in the README
> (https://github.com/tohojo/netperf-wrapper#quick-start) or read the man
> page.
>
> -Toke
>

[-- Attachment #2: Type: text/html, Size: 4248 bytes --]

  reply	other threads:[~2015-04-17 14:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17  5:22 sahil grover
2015-04-17  6:48 ` Andrew McGregor
2015-04-17  9:04   ` sahil grover
2015-04-17 11:15     ` Andrew McGregor
2015-04-17 12:42     ` Toke Høiland-Jørgensen
2015-04-17 14:52       ` sahil grover [this message]
2015-04-17 15:49         ` sahil grover
2015-04-17 16:25           ` Rick Jones
2015-04-18 12:42             ` Toke Høiland-Jørgensen
2015-04-20 12:05               ` sahil grover
2015-04-20 15:26                 ` Toke Høiland-Jørgensen
2015-04-20 15:43                   ` sahil grover
2015-04-21  8:57                     ` Toke Høiland-Jørgensen
2015-04-21  9:57                       ` sahil grover
2015-04-21 13:30                         ` Toke Høiland-Jørgensen
2015-04-21 14:51                           ` sahil grover
2015-04-21 15:35                             ` sahil grover
2015-04-21 16:19                               ` sahil grover
2015-04-21 19:19                                 ` Jonathan Morton
2015-04-21 16:07                           ` Rick Jones
2015-04-17 16:56         ` Jonathan Morton

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=CADnS-2g+OneXB1aapFe68hhZyDeAwJ9tLD1_ZnBOysCnC3ni4w@mail.gmail.com \
    --to=sahilgrover013@gmail.com \
    --cc=codel@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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