From: Ferruh Yigit <ferruh.yigit@intel.com>
To: ido goshen <ido@cgstowernetworks.com>,
Bruce Richardson <bruce.richardson@intel.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4] net/pcap: rx_iface_in stream type support
Date: Wed, 4 Jul 2018 18:55:14 +0100 [thread overview]
Message-ID: <32315529-cfaf-6668-8700-4cd46a81b4d0@intel.com> (raw)
In-Reply-To: <10b1cffd-6c11-0a5b-dd59-ce239611d3d7@intel.com>
On 7/3/2018 7:37 PM, Ferruh Yigit wrote:
> On 7/1/2018 12:05 PM, ido goshen wrote:
>> From: ido g <ido@cgstowernetworks.com>
>>
>> Support rx of in direction packets only
>> Useful for apps that also tx to eth_pcap ports in order to not see them
>> echoed back in as rx when out direction is also captured
>>
>> Example:
>> In case using rx_iface and sending *single* packet to eth1
>> it will loop forever as the when it is sent to tx_iface=eth1
>> it will be captured again on the rx_iface=eth1 and so on
>> $RTE_TARGET/app/testpmd l 0-3 -n 4 \
>> --vdev 'net_pcap0,rx_iface=eth1,tx_iface=eth1'
>> …
>> ---------------------- Forward statistics for port 0 ------------
>> RX-packets: 758 RX-dropped: 0 RX-total: 758
>> TX-packets: 758 TX-dropped: 0 TX-total: 758
>> ------------------------------------------------------------------
>> While if using rx_iface_in it will not be captured on the way out and
>> be forwarded only once
>> $RTE_TARGET/app/testpmd l 0-3 -n 4 \
>> --vdev 'net_pcap0,rx_iface_in=eth1,tx_iface=eth1'
>> …
>> ---------------------- Forward statistics for port 0 ------------
>> RX-packets: 1 RX-dropped: 0 RX-total: 1
>> TX-packets: 1 TX-dropped: 0 TX-total: 1
>> ------------------------------------------------------------------
>>
>> Signed-off-by: ido g <ido@cgstowernetworks.com>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-07-04 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 11:05 ido goshen
2018-07-03 18:37 ` Ferruh Yigit
2018-07-04 17:55 ` Ferruh Yigit [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=32315529-cfaf-6668-8700-4cd46a81b4d0@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ido@cgstowernetworks.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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 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).