All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denys" <denys@visp.net.lb>
To: Patrick McHardy <kaber@trash.net>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
	Stephen Hemminger <shemminger@linux-foundation.org>
Subject: Re: iproute2-2.6.20-070313 bug ?
Date: Thu, 22 Mar 2007 15:47:54 +0200	[thread overview]
Message-ID: <20070322134552.M83364@visp.net.lb> (raw)
In-Reply-To: <4602880F.1010403@trash.net>

Hi again

On Thu, 22 Mar 2007 14:43:43 +0100, Patrick McHardy wrote
> Denys wrote:
> >>>Another thing, it is working well 
> >>>with old tc. Just really if i have plenty of RAM's and i want 32second 
> >>>buffer, why i cannot have that, and if i see it is really possible 
before?
> >>
> >>I know it worked before. But I can't think of a reason why anyone
> >>would want a buffer that large. Why do you want to queue packets
> >>for up to 64 seconds?
> > 
> > Seems i misunderstand how it works. If i am not wrong, till buffer 
available, 
> > bandwidth will be given on "peakrate" speed, and when buffer is empty - 
on 
> > "rate" speed. I am wrong?
> 
> No, I got confused, sorry about that. Your configuration allows 
> bursts up to 64 seconds long. I guess there's nothing wrong with that.
> 
> I already asked Stephen to revert that patch, it was not meant to
> be included yet, unfortunately it made it into the release. Even
> more unfortunate is that it looks like we need larger types in the
> ABI to properly support nano-second resolution.

Thanks sir for your great help and great software and sorry that i took time, 
by not enough good explanation. 

--
Virtual ISP S.A.L.


  reply	other threads:[~2007-03-22 13:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 18:00 iproute2-2.6.20-070313 bug ? Denys
2007-03-22 11:23 ` Patrick McHardy
2007-03-22 12:46   ` Denys
2007-03-22 13:09     ` Patrick McHardy
     [not found]       ` <20070322131245.M85528@visp.net.lb>
2007-03-22 13:23         ` Patrick McHardy
2007-03-22 13:35           ` Denys
     [not found]           ` <20070322132637.M88445@visp.net.lb>
2007-03-22 13:43             ` Patrick McHardy
2007-03-22 13:47               ` Denys [this message]
2007-03-22 13:26       ` Denys
2007-03-22 17:12       ` Stephen Hemminger
2007-03-22 17:14         ` Patrick McHardy
2007-03-26 18:49           ` more... iproute2/htb/whatever critical " Denys
2007-03-27 15:10             ` Patrick McHardy
2007-03-27 15:18               ` Denys
2007-03-27 16:00               ` Denys
2007-03-27 16:21                 ` Patrick McHardy
2007-03-28 17:38                   ` another " Denys
2007-03-28 23:55                   ` Denys
2007-03-29 10:58                     ` Patrick McHardy
2007-03-31  2:26         ` more iproute2 issues (not critical) Denys
2007-03-31  2:31           ` Denys
2007-03-31 14:16             ` Patrick McHardy
2007-04-04  0:03         ` one more... iproute commands lockup whole system Denys
2007-04-04  1:10           ` jamal
2007-04-04  1:39             ` Patrick McHardy
2007-04-04  2:09               ` jamal
2007-04-04  2:11               ` Denys
2007-04-04 10:55                 ` jamal
2007-04-04 12:56                   ` Denys
2007-04-04 14:10                     ` jamal
2007-04-04 14:35                       ` Denys
2007-04-04 14:13                     ` HTB/act_mirred problem [was: one more... iproute commands lockup whole system] Patrick McHardy
2007-04-04 14:33                       ` jamal
2007-04-04 14:50                         ` Patrick McHardy
2007-04-05  1:33                           ` jamal
2007-04-04 13:36                   ` one more... iproute commands lockup whole system Patrick McHardy
2007-04-04 13:58                     ` jamal
2007-04-04 14:07                       ` Patrick McHardy
2007-04-04 14:30                         ` jamal
2007-04-04 14:39                           ` Patrick McHardy
2007-04-05  2:14                             ` jamal

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=20070322134552.M83364@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.