From: jamal <hadi@cyberus.ca>
To: Ben Greear <greearb@candelatech.com>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
NetDev <netdev@vger.kernel.org>
Subject: Re: pktgen patch available for perusal.
Date: Sat, 04 Nov 2006 07:32:12 -0500 [thread overview]
Message-ID: <1162643532.5166.34.camel@jzny2> (raw)
In-Reply-To: <4548F166.1020001@candelatech.com>
On Wed, 2006-01-11 at 11:11 -0800, Ben Greear wrote:
> I'd be thrilled to have the receive logic go into pktgen, even if
> it was #if 0 with a comment
> showing how to patch dev.c to get it working. It would make my
> out-of-tree patch smaller
> and should help others who are doing research and driver development...
>
I use pktgen extensively these days for ipsec testing. I also record
stats for pkts i receive using a tc action drop. Very simple and works
great.
Ben, you keep insisting on doing this hook (every 3 months) because you
dont want to invest time to do it with netlink (I thought you sold this
as part of your product - the investment of your time is really not that
high). If you tell me what the packet trigger is, I will send you a
script ;->
Robert, I have started writing some generic netlink messaging to replace
the /proc that i will send your way. I need to get consensus on some
tunnel-mode IPSEC patches first then i will send the about three
patchsets your way (to replace the old ones i sent earlier).
cheers,
jamal
next prev parent reply other threads:[~2006-11-04 12:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 23:47 pktgen patch available for perusal Ben Greear
2006-11-01 17:14 ` Robert Olsson
2006-11-01 19:11 ` Ben Greear
2006-11-03 11:13 ` Robert Olsson
2006-11-03 16:34 ` Ben Greear
2006-11-03 20:24 ` Robert Olsson
2006-11-03 20:41 ` Ben Greear
2006-11-04 12:32 ` jamal [this message]
2006-11-04 17:29 ` Ben Greear
2006-11-04 18:10 ` jamal
2006-11-04 19:12 ` Ben Greear
2006-11-06 14:06 ` Robert Olsson
2006-11-06 14:14 ` Robert Olsson
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=1162643532.5166.34.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=Robert.Olsson@data.slu.se \
--cc=greearb@candelatech.com \
--cc=netdev@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.