All of lore.kernel.org
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] measuring queueing delay using iproute2
Date: Wed, 27 Feb 2002 07:55:52 +0000	[thread overview]
Message-ID: <marc-lartc-101479659726516@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101477184406327@msgid-missing>

On Tue, Feb 26, 2002 at 05:02:45PM -0800, Radhakrishnan Vijay wrote:
> I am using the tc functionality provided by iproute2
> to setup classes and queueing disciplines. I have a
> requirement to determine the queueing delay of each
> packet belonging to a particular class so that i can
> measure the average queueing delay over a time
> interval for a particular traffic class. I would be
> grateful if somebody could give me pointers on how i
> possibly can achieve this. I suspect that i would have
> to modify the source code of iproute2 , but am not too
> sure on what segment of the code i should be
> modifying.

Right now the actual delay is not measured by the kernel, so I don't see how
you would get at it. You could calculate the effective class bandwidth and
multiply that by the average qlength, but that would be pretty indirect.

Regards,

bert

-- 
http://www.PowerDNS.com          Versatile DNS Software & Services
http://www.tk                              the dot in .tk
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  reply	other threads:[~2002-02-27  7:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27  1:02 [LARTC] measuring queueing delay using iproute2 Radhakrishnan Vijay
2002-02-27  7:55 ` bert hubert [this message]
2002-02-27  8:55 ` Martin Devera

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-101479659726516@msgid-missing \
    --to=ahu@ds9a.nl \
    --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.