From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] measuring performance time in a node using ethereal/tcpdump
Date: Fri, 29 Nov 2002 18:09:12 +0000 [thread overview]
Message-ID: <marc-lartc-103859345305271@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103852936325473@msgid-missing>
On Friday 29 November 2002 01:21, nitin panjwani wrote:
> Hi All,
>
> We are doing some experiment, where we are trying to
> measure the processing time taken by a node when a
> packate pssess throgh it.
>
> --------eth0[Linux-PC Router]eth1-------
>
> We run tethereal within this PC at eth0(incomming
> interface) and eth1(outgoing interface) . Then we find
> out our packate in both the captures and the
> difference of two captures gives processing time of
> the node
>
> Now, the question: Is doing so a right way to measure
> the processing time, as we are not sure where exactly
> does libcap captures the packates. Is it right before
> network driver or after it ao anywhere else?
>
> I just came to know that On Linux, libpcap captures
> packets using PF_PACKET sockets (or, on 2.0
> kernels or with libpcap built on a 2.0-kernel system,
> PF_INET/SOCK_PACKET sockets).
>
> Any help on this issue will be highly appreciable.
Why not using 2 extra boxes. If you send a packet from left to right and the
right hosts responds immediate (ping or so), so the packet returns, you know
the processing time.
I think there are also traffic generator tools that can monitor delays and
jitter.
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/
next prev parent reply other threads:[~2002-11-29 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 0:21 [LARTC] measuring performance time in a node using ethereal/tcpdump nitin panjwani
2002-11-29 18:09 ` Stef Coene [this message]
2002-11-30 1:40 ` Martin A. Brown
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-103859345305271@msgid-missing \
--to=stef.coene@docum.org \
--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.