DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Maxim Uvarov <maxim.uvarov@linaro.org>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "tero.aho@coriant.com" <tero.aho@coriant.com>
Subject: Re: [dpdk-dev] [PATCH] support jumbo frames for pcap vdev
Date: Tue, 9 Jun 2015 12:15:17 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2F34927@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1433844923-29797-1-git-send-email-maxim.uvarov@linaro.org>

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Maxim Uvarov
> Sent: Tuesday, June 9, 2015 11:15 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] support jumbo frames for pcap vdev
> 
> PCAP PMD vdev is used mostly for testing. Increase snapshot len parameter
> provided to pcap_open_live() to accept packet more then 4096 (support
> jumbo frames for pcap pmd).

Hi,

Thanks for the submission.

There is already an existing patch for jumbo frame support in the PCAP pmd.

    http://dpdk.org/dev/patchwork/patch/3792/

Could you review/try that and see if it is suitable for your purposes.

Regards,

John.
-- 








> 
> Signed-off-by: Maxim Uvarov <maxim.uvarov@linaro.org>
> ---
>  lib/librte_pmd_pcap/rte_eth_pcap.c | 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/lib/librte_pmd_pcap/rte_eth_pcap.c
> b/lib/librte_pmd_pcap/rte_eth_pcap.c
> index eebe768..978c137 100644
> --- a/lib/librte_pmd_pcap/rte_eth_pcap.c
> +++ b/lib/librte_pmd_pcap/rte_eth_pcap.c
> @@ -47,7 +47,6 @@
>  #include <pcap.h>
> 
>  #define RTE_ETH_PCAP_SNAPSHOT_LEN 65535 -#define RTE_ETH_PCAP_SNAPLEN
> 4096  #define RTE_ETH_PCAP_PROMISC 1  #define RTE_ETH_PCAP_TIMEOUT -1
> #define ETH_PCAP_RX_PCAP_ARG  "rx_pcap"
> @@ -468,7 +467,7 @@ open_tx_pcap(const char *key __rte_unused, const char
> *value, void *extra_args)
>   */
>  static inline int
>  open_iface_live(const char *iface, pcap_t **pcap) {
> -	*pcap = pcap_open_live(iface, RTE_ETH_PCAP_SNAPLEN,
> +	*pcap = pcap_open_live(iface, RTE_ETH_PCAP_SNAPSHOT_LEN,
>  			RTE_ETH_PCAP_PROMISC, RTE_ETH_PCAP_TIMEOUT, errbuf);
> 
>  	if (*pcap == NULL) {
> --
> 1.9.1

  reply	other threads:[~2015-06-09 12:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 10:15 Maxim Uvarov
2015-06-09 12:15 ` Mcnamara, John [this message]
2015-06-09 12:50   ` Maxim Uvarov
2015-06-26 14:04     ` Thomas Monjalon
2015-06-26 14:10       ` Mcnamara, John

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=B27915DBBA3421428155699D51E4CFE2F34927@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=maxim.uvarov@linaro.org \
    --cc=tero.aho@coriant.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).