From: David Miller <davem@davemloft.net>
To: daniel.turull@gmail.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org,
robert@herjulf.net, jens.laas@its.uu.se, voravit@kth.se
Subject: Re: [PATCH 2/2] pktgen: receive packets and process incoming rate
Date: Tue, 15 Jun 2010 14:59:48 -0700 (PDT) [thread overview]
Message-ID: <20100615.145948.68117816.davem@davemloft.net> (raw)
In-Reply-To: <4C10F117.60800@gmail.com>
From: Daniel Turull <daniel.turull@gmail.com>
Date: Thu, 10 Jun 2010 16:05:11 +0200
> This patch adds receiver part to pktgen taking advantages of SMP systems
> with multiple rx queues:
> - Creation of new proc file /proc/net/pktgen/pgrx to control and display the receiver.
> - It uses PER-CPU variable to store the results per each CPU.
> - Results displayed per CPU and aggregated.
> - The packet handler is add in the protocols handlers (dev_add_pack())
> - Available statistics: packets and bytes received, work time and rate
> - Only process pktgen packets
> - It is possible to select the incoming interface
> - Documentation updated with the new commands to control the receiver part.
>
> Signed-off-by: Daniel Turull <daniel.turull@gmail.com>
I completely disagree with this patch on two levels:
1) pktgen is for "generating" packets, not receiving them.
Trying to put lipstick on a pig is never a good idea.
2) The information it gathers and shows is completely useless.
What's interesting as "RX work cost" is what happens deep
down in the netif_receive_skb() code paths, IP input, routing,
netfilter, whatever... but that is not what this thing is
measuring at all.
Sorry, I'm not applying this. You can probably do something more
clever with tracepoints.
prev parent reply other threads:[~2010-06-15 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 11:49 [PATCH 2/2] pktgen: receive packets and process incoming rate Daniel Turull
2010-06-02 13:00 ` Eric Dumazet
2010-06-02 13:28 ` Daniel Turull
2010-06-10 14:04 ` Daniel Turull
2010-06-10 14:05 ` Daniel Turull
2010-06-15 21:59 ` David Miller [this message]
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=20100615.145948.68117816.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=daniel.turull@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=jens.laas@its.uu.se \
--cc=netdev@vger.kernel.org \
--cc=robert@herjulf.net \
--cc=voravit@kth.se \
/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).