All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Watson <David.Watson@team17.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen)
Date: Fri, 20 Jun 2003 15:20:05 +0000	[thread overview]
Message-ID: <marc-lartc-105612275605290@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105593587226514@msgid-missing>


         I was recreating the qdiscs so that changes would be picked up 
automatically and not disturb the rrdtool generation, I've switched to a 
counter and cut out the resets.

         I did do a lot of ping tests and cannot replicate losing packets 
however.

Thanks

At 21:55 18/06/2003 +0200, you wrote:
>On Wednesday 18 June 2003 21:17, Giannis Stoilis wrote:
> > Stef Coene wrote:
> > > On Wednesday 18 June 2003 20:53, Giannis Stoilis wrote:
> > >>Never mind that. The most important issue here is that when you delete
> > >>your queues, any packet that happens to pass through them at that time,
> > >>are LOST!
> > >
> > > Are you sure?  I never tested it.
> >
> > This is how I know it:
> > I constantly ping my linux server from another pc. At some poing I
> > delete and recreate my queues. From the pc that pings my linux server, I
> > can see the replies coming, and at the point of the restart I have
> > missed pinging replies and at the point after the qdisc creation, I can
> > see the icmp replies coming back again.
> > Either every packet is lost at qdisc removal, or something else, same as
> > nasty, is happening...
> > You should try it and see...
> > Also, if you have monitor_tc running at that time, you can see it dump
> > some nice negative values...
>:)
>That's because the counters are resetten so the values are negative at that
>time.  But that will not say are packets are gone.  However, your ping test
>proves it.
>
>Stef
>
>--
>
>stef.coene@docum.org
>  "Using Linux as bandwidth manager"
>      http://www.docum.org/
>      #lartc @ irc.oftc.net
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-06-20 15:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-18 11:29 [LARTC] HTB Kernel log (cl && cl->un.leaf.q->q.qlen) David Watson
2003-06-18 16:43 ` Stef Coene
2003-06-18 18:53 ` Giannis Stoilis
2003-06-18 19:10 ` Stef Coene
2003-06-18 19:17 ` Giannis Stoilis
2003-06-18 19:55 ` Stef Coene
2003-06-20 15:20 ` David Watson [this message]
2003-06-20 19:41 ` Giannis Stoilis
2003-07-03 12:06 ` Stef Coene

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=marc-lartc-105612275605290@msgid-missing \
    --to=david.watson@team17.com \
    --cc=lartc@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 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.