From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Maxim Uvarov <maxim.uvarov@linaro.org>,
"tero.aho@coriant.com" <tero.aho@coriant.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Bill Fischofer <bill.fischofer@linaro.org>
Subject: Re: [dpdk-dev] [PATCH] support jumbo frames for pcap vdev
Date: Fri, 26 Jun 2015 14:10:39 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2F5D68E@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <4834004.3WCpfd7CLu@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Friday, June 26, 2015 3:04 PM
> To: Maxim Uvarov; Mcnamara, John; tero.aho@coriant.com
> Cc: dev@dpdk.org; Bill Fischofer
> Subject: Re: [dpdk-dev] [PATCH] support jumbo frames for pcap vdev
>
> 2015-06-09 15:50, Maxim Uvarov:
> > On 06/09/15 15:15, Mcnamara, John wrote:
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Maxim Uvarov
> > >> 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).
> > >
> > > 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.
> >
> > Thanks, I did not see that patch. I see that your patch supports
> > segmentation also. Will do test in my environment.
>
> Any update?
Hi Thomas,
I hope to rework and resubmit it early next week.
John.
--
prev parent reply other threads:[~2015-06-26 14:10 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
2015-06-26 14:04 ` Thomas Monjalon
2015-06-26 14:10 ` Mcnamara, John [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=B27915DBBA3421428155699D51E4CFE2F5D68E@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=bill.fischofer@linaro.org \
--cc=dev@dpdk.org \
--cc=maxim.uvarov@linaro.org \
--cc=tero.aho@coriant.com \
--cc=thomas.monjalon@6wind.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).