From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] cmdline: increase commandline buffer size to 512
Date: Mon, 9 Nov 2015 16:54:25 +0100 [thread overview]
Message-ID: <20151109155425.GK1968@autoinstall.dev.6wind.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2023B3D77@IRSMSX103.ger.corp.intel.com>
On Mon, Nov 09, 2015 at 11:45:04AM +0000, Mcnamara, John wrote:
>
>
> > -----Original Message-----
> > From: Nélio Laranjeiro [mailto:nelio.laranjeiro@6wind.com]
> > Sent: Thursday, November 5, 2015 4:51 PM
> > To: Mcnamara, John; Olivier Matz; Thomas Monjalon
> > Cc: dev@dpdk.org
> > Subject: Re: [dpdk-dev] [PATCH] cmdline: increase commandline buffer size
> > to 512
> >
> > On Thu, Nov 05, 2015 at 09:58:36AM +0000, John McNamara wrote:
> > > Increase commandline buffer size to 512 to allow for longer
> > > commandlines required by testpmd when dealing with flow director and
> > > IPv6 addresses.
> > >
> > > ...
> > >
> > > /* configuration */
> > > -#define RDLINE_BUF_SIZE 256
> > > +#define RDLINE_BUF_SIZE 512
> > >
> >
> > I have faced the same issue. For some commands this value is still too
> > low. For example, RETA update can not be used, the command line limits
> > he configuration to 34 entries.
> >
> > See http://dpdk.org/ml/archives/dev/2015-October/024681.html
> > and particularly
> > http://dpdk.org/ml/archives/dev/2015-October/024682.html
> >
> > It was too late to announce an ABI change so we left out the cmdline
> > size update.
> >
> > Olivier, Thomas, what do you think about this? It seems this is really
> > blocking.
>
> Hi,
>
> Since the change breaks ABI I'll self nack.
>
> However, this is something that should be fixed since it will affect any DPDK application with a long commandline.
>
> I can put a warning of future ABI breakage in the release notes but I see that there are other #defines that you need to increase in your patchset so do you want to submit the ABI deprecation notice?
>
> John.
> --
Hi John,
I will do it, I have another depreciation related to RETA.
Thanks.
--
Nélio Laranjeiro
6WIND
prev parent reply other threads:[~2015-11-09 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 9:58 John McNamara
2015-11-05 16:50 ` Nélio Laranjeiro
2015-11-09 11:45 ` Mcnamara, John
2015-11-09 15:54 ` Nélio Laranjeiro [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=20151109155425.GK1968@autoinstall.dev.6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).