From: David Marchand <david.marchand@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 0/3] remove limit on devargs parameters length
Date: Fri, 13 Feb 2015 16:03:12 +0100 [thread overview]
Message-ID: <1423839795-29450-1-git-send-email-david.marchand@6wind.com> (raw)
In-Reply-To: <1420635809-30976-1-git-send-email-david.marchand@6wind.com>
Here is a little patchset that removes the limit on the devargs parameters
length. Previously, arguments specified by user would be stored in a static
buffer, while there is no particular reason why we should have such a
constraint, afaik.
Changes since v1:
- fix devargs tests (problem reported by Thomas)
--
David Marchand
David Marchand (3):
devargs: indent and cleanup
devargs: remove limit on parameters length
app/test: fix devargs tests
app/test/test_devargs.c | 6 ++--
app/test/test_pci.c | 2 ++
lib/librte_eal/common/eal_common_devargs.c | 51 ++++++++++++++++-----------
lib/librte_eal/common/include/rte_devargs.h | 4 +--
4 files changed, 38 insertions(+), 25 deletions(-)
--
1.7.10.4
next prev parent reply other threads:[~2015-02-13 15:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 13:03 [dpdk-dev] [PATCH 0/2] " David Marchand
2015-01-07 13:03 ` [dpdk-dev] [PATCH 1/2] devargs: indent and cleanup David Marchand
2015-01-07 13:03 ` [dpdk-dev] [PATCH 2/2] devargs: remove limit on parameters length David Marchand
2015-01-07 22:59 ` Stephen Hemminger
2015-01-08 8:19 ` David Marchand
2015-01-08 9:15 ` Panu Matilainen
2015-02-13 15:03 ` David Marchand [this message]
2015-02-13 15:03 ` [dpdk-dev] [PATCH v2 1/3] devargs: indent and cleanup David Marchand
2015-02-13 15:03 ` [dpdk-dev] [PATCH v2 2/3] devargs: remove limit on parameters length David Marchand
2015-02-13 15:03 ` [dpdk-dev] [PATCH v2 3/3] app/test: fix devargs tests David Marchand
2015-02-18 12:44 ` [dpdk-dev] [PATCH v2 0/3] remove limit on devargs parameters length Thomas Monjalon
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=1423839795-29450-1-git-send-email-david.marchand@6wind.com \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
/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).