All of lore.kernel.org
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: josh@freedesktop.org, mm-commits@vger.kernel.org
Subject: - allow-pktgen-to-work-with-loopback-devices.patch removed from -mm tree
Date: Thu, 22 Mar 2007 22:52:55 -0800	[thread overview]
Message-ID: <200703230652.l2N6qtXQ008409@shell0.pdx.osdl.net> (raw)


The patch titled
     Allow pktgen to work with loopback devices.
has been removed from the -mm tree.  Its filename was
     allow-pktgen-to-work-with-loopback-devices.patch

This patch was dropped because an updated version will be merged

------------------------------------------------------
Subject: Allow pktgen to work with loopback devices.
From: Josh Triplett <josh@freedesktop.org>

pktgen currently only works on network devices with type ARPHRD_ETHER.  Add
support for the loopback device, type ARPHRD_LOOPBACK.

I've tested this on my system, using a modified pktgen.conf-1-1 with
s/eth1/lo/g, and it works fine; the network device statistics confirm
packet transmission and receipt.

Thanks to Sarah Bailey for discovering and tracking down the problem.

Signed-off-by: Josh Triplett <josh@freedesktop.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 net/core/pktgen.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff -puN net/core/pktgen.c~allow-pktgen-to-work-with-loopback-devices net/core/pktgen.c
--- a/net/core/pktgen.c~allow-pktgen-to-work-with-loopback-devices
+++ a/net/core/pktgen.c
@@ -1929,7 +1929,7 @@ static int pktgen_setup_dev(struct pktge
 		return -ENODEV;
 	}
 
-	if (odev->type != ARPHRD_ETHER) {
+	if (odev->type != ARPHRD_LOOPBACK && odev->type != ARPHRD_ETHER) {
 		printk("pktgen: not an ethernet device: \"%s\"\n", ifname);
 		err = -EINVAL;
 	} else if (!netif_running(odev)) {
_

Patches currently in -mm which might be from josh@freedesktop.org are

allow-pktgen-to-work-with-loopback-devices.patch
rcutorture-mark-rcu_torture_init-as-__init.patch

                 reply	other threads:[~2007-03-23  6:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200703230652.l2N6qtXQ008409@shell0.pdx.osdl.net \
    --to=akpm@linux-foundation.org \
    --cc=josh@freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@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.