DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxim Uvarov <maxim.uvarov@linaro.org>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "tero.aho@coriant.com" <tero.aho@coriant.com>,
	Bill Fischofer <bill.fischofer@linaro.org>
Subject: Re: [dpdk-dev] [PATCH] support jumbo frames for pcap vdev
Date: Tue, 09 Jun 2015 15:50:55 +0300	[thread overview]
Message-ID: <5576E12F.4030200@linaro.org> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2F34927@IRSMSX103.ger.corp.intel.com>

On 06/09/15 15:15, Mcnamara, John wrote:
>> -----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.
Thanks, I did not see that patch. I see that your patch supports 
segmentation also. Will do test in my environment.

Maxim.

  reply	other threads:[~2015-06-09 12:50 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
2015-06-09 12:50   ` Maxim Uvarov [this message]
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=5576E12F.4030200@linaro.org \
    --to=maxim.uvarov@linaro.org \
    --cc=bill.fischofer@linaro.org \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --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).