DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ido Goshen <Ido@cgstowernetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/pcap: rx_iface_in stream type support
Date: Wed, 13 Jun 2018 11:57:27 +0100	[thread overview]
Message-ID: <f4fbaa7c-0cd3-5415-5ba6-19eb475c6ef5@intel.com> (raw)
In-Reply-To: <HE1PR0901MB1436CF58910B8A05010C77D5D6660@HE1PR0901MB1436.eurprd09.prod.outlook.com>

On 6/5/2018 6:10 PM, Ido Goshen wrote:
> The problem is if a dpdk app uses the same iface(s) both as rx_iface and tx_iface then it will receive back the packets it sends.
> If my app sends a packet to portid=X with rte_eth_tx_burst() then I wouldn't expect to receive it back by rte_eth_rx_burst() for that same portid=X  (assuming of course there's no external loopback)
> This is coming from the default nature of pcap that like a sniffer captures both incoming and outgoing direction.
> The patch provides an option to limit pcap rx_iface to get only incoming traffic which is more like a real (non-pcap) dpdk device.
> 
> for example:
> when using existing *rx_iface*
> 	l2fwd -c 3 -n1 --no-huge --vdev=eth_pcap0,rx_iface=eth1,tx_iface=eth1 --vdev=eth_pcap1,rx_iface=dummy0,tx_iface=dummy0  -- -p 3 -T 1 
> sending only 1 single packet into eth1 will end in an infinite loop - 

If you are using same interface for both Rx & Tx, why not using "iface=xxx"
argument, can you please test with following:

l2fwd -c 3 -n1 --no-huge --vdev=eth_pcap0,iface=eth1
--vdev=eth_pcap1,iface=dummy0 -- -p 3 -T 1


I can't reproduce the issue with above command.

Thanks,
ferruh

  reply	other threads:[~2018-06-13 10:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05  9:39 ido goshen
2018-06-05 13:26 ` Ferruh Yigit
2018-06-05 17:10   ` Ido Goshen
2018-06-13 10:57     ` Ferruh Yigit [this message]
2018-06-14 17:14       ` Ido Goshen
2018-06-14 18:09         ` Ferruh Yigit
2018-06-14 20:44           ` Ido Goshen
2018-06-15 12:53             ` Ferruh Yigit
2018-06-16  9:27               ` Ido Goshen
2018-06-18  8:13                 ` Ferruh Yigit
2018-06-18  9:49                   ` Ido Goshen
2018-06-20 18:04                     ` Ferruh Yigit

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=f4fbaa7c-0cd3-5415-5ba6-19eb475c6ef5@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=Ido@cgstowernetworks.com \
    --cc=dev@dpdk.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 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).