netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: Jarek Poplawski <jarkao2@o2.pl>, netdev@vger.kernel.org
Subject: Re: HTB/HSFC shaping precision
Date: Wed, 21 Nov 2007 10:06:47 -0500	[thread overview]
Message-ID: <1195657607.4437.8.camel@localhost> (raw)
In-Reply-To: <20071121103024.M12218@visp.net.lb>

On Wed, 2007-21-11 at 12:31 +0200, Denys Fedoryshchenko wrote:
> On Wed, 21 Nov 2007 10:47:10 +0100, Jarek Poplawski wrote
> > 
> > But, if you have full control on your side, it looks like a kind of
> > realtime traffic, and then HFSC should be more appropriate for this
> > (but I only 'heard' about this).
> 
> One message later, thats what i dreamed about :-)
> Subject: [RFC][PATCH 1/3] NET_SCHED: PSPacer qdisc module 
> On website they have very good explanation... 
> http://www.gridmpi.org/gridtcp.jsp

That looks interesting - without reading the papers a few questions are
developing in my brain cells; for example it looks very similar to what
the chelsio NICs claim to do (which could be a good thing for TCP).
Whenever i see someone implementing something in hardware, i always get
flushes of "patents". 

Denys, one of the things i have noticed with iperf is it tries to be
clever and "probe" the available bandwidth first. So you may not get the
most optimal use of of your bandwidth. Try something like pktgen, its
quiet accurate in its measurements. Just add a tc drop rule on the
receiver to get the accounting.

cheers,
jamal


  reply	other threads:[~2007-11-21 15:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19  8:55 HTB/HSFC shaping precision Denys Fedoryshchenko
2007-11-19 16:24 ` jamal
2007-11-20  9:43   ` Denys Fedoryshchenko
2007-11-20 20:00     ` Jarek Poplawski
2007-11-20 21:21       ` Denys Fedoryshchenko
2007-11-21  9:47         ` Jarek Poplawski
2007-11-21 10:31           ` Denys Fedoryshchenko
2007-11-21 15:06             ` jamal [this message]
2007-11-22  2:07               ` Ryousei Takano

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1195657607.4437.8.camel@localhost \
    --to=hadi@cyberus.ca \
    --cc=denys@visp.net.lb \
    --cc=jarkao2@o2.pl \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).