From: Ben Greear <greearb@candelatech.com>
To: jamal <hadi@cyberus.ca>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Enable sending network traffic to local machine over external interfaces.
Date: Sun, 15 Sep 2002 13:40:35 -0700 [thread overview]
Message-ID: <3D84F043.1070409@candelatech.com> (raw)
In-Reply-To: Pine.GSO.4.30.0209151616280.22001-100000@shell.cyberus.ca
jamal wrote:
> What bad stuff are you smoking lately? Trying to turn linux into a traffic
> generator OS? ;-> Havent you been accused of that already?
> Actually, this is probably one of the few times i agree with you because i
> may have use for this; i dont think the maintainers may. Infact i think
> you are just about to be shot.
> How about putting ifdefs so that the code only gets activated if
> packetgen is active?
>
> cheers,
> jamal
>
Pktgen is independent of this particular hack. One of the flag #defines is in the
patch to make my life easier, but it can be removed if that makes someone happier...
Right now, I am getting panics after 30 minutes running at around 250Mbps of tcp traffic to
myself over GigE nics. But, I'm running NAPI e1000, the send-to-self hack, and
had the pktgen module loaded.... Trying to narrow it down...but so far, it looks
like memory corruption, perhaps somewhere in tcp/ip...
It can still be #ifdef'd, but some of the code just fixes the SO_BINDTODEVICE
feature, so I think that may be worth putting in anyway...
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
prev parent reply other threads:[~2002-09-15 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 6:44 [PATCH] Enable sending network traffic to local machine over external interfaces Ben Greear
2002-09-15 20:22 ` jamal
2002-09-15 20:40 ` Ben Greear [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=3D84F043.1070409@candelatech.com \
--to=greearb@candelatech.com \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
/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.