From: Pawel Wodkowski <pawelx.wodkowski@intel.com>
To: Olivier MATZ <olivier.matz@6wind.com>,
Pawel Wodkowski <pwodkowx@stargo.org>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] cmdline: add polling mode for command line
Date: Tue, 12 May 2015 18:14:53 +0200 [thread overview]
Message-ID: <555226FD.2060509@intel.com> (raw)
In-Reply-To: <55521003.1080805@6wind.com>
On 2015-05-12 16:36, Olivier MATZ wrote:
> Hi Pawel,
>
> On 05/12/2015 01:10 PM, Pawel Wodkowski wrote:
>> This patch adds the ability to process console input in the same thread
>> as packet processing by using poll() function.
>>
>> Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com>
>> [...]
>> --- a/lib/librte_cmdline/cmdline.h
>> +++ b/lib/librte_cmdline/cmdline.h
>> @@ -84,6 +84,7 @@ void cmdline_printf(const struct cmdline *cl, const
>> char *fmt, ...)
>> __attribute__((format(printf,2,3)));
>> int cmdline_in(struct cmdline *cl, const char *buf, int size);
>> int cmdline_write_char(struct rdline *rdl, char c);
>> +int cmdline_poll(struct cmdline *cl);
>> void cmdline_interact(struct cmdline *cl);
>> void cmdline_quit(struct cmdline *cl);
>>
>> diff --git a/lib/librte_cmdline/rte_cmdline_version.map
>> b/lib/librte_cmdline/rte_cmdline_version.map
>> index 6193462..df55def 100644
>
> I know the rest of the file does not document the functions
> prototypes, but I think it could be helpful to add doxygen-style
> comments for new functions.
Yes, no problem.
>
>> diff --git a/lib/librte_cmdline/rte_cmdline_version.map
>> b/lib/librte_cmdline/rte_cmdline_version.map
>> index 6193462..df55def 100644
>> --- a/lib/librte_cmdline/rte_cmdline_version.map
>> +++ b/lib/librte_cmdline/rte_cmdline_version.map
>> @@ -40,6 +40,7 @@ DPDK_2.0 {
>> cmdline_parse_num;
>> cmdline_parse_portlist;
>> cmdline_parse_string;
>> + cmdline_poll;
>> cmdline_printf;
>> cmdline_quit;
>> cmdline_set_prompt;
>>
>
> I'm not sure the .map should be modified like this, instead I
> would have added a new DPDK_2.1 section, like I did for this
> commit (reviewed by Neil):
> http://dpdk.org/browse/dpdk/commit/?id=bbd778248985e542175e9b4ce560f2d379e78c4e
>
>
> By the way, the following link is a good documentation about the
> .map files:
> http://people.freebsd.org/~deischen/symver/freebsd_versioning.txt
Thank you, I will follow those instructions :)
Please check v2 I will send shortly.
--
Pawel
next prev parent reply other threads:[~2015-05-12 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 11:10 [dpdk-dev] [PATCH 0/2] " Pawel Wodkowski
2015-05-12 11:10 ` [dpdk-dev] [PATCH 1/2] cmdline: fix missing include files Pawel Wodkowski
2015-05-12 11:10 ` [dpdk-dev] [PATCH 2/2] cmdline: add polling mode for command line Pawel Wodkowski
2015-05-12 14:36 ` Olivier MATZ
2015-05-12 16:14 ` Pawel Wodkowski [this message]
2015-05-12 11:36 ` [dpdk-dev] [PATCH 0/2] " Dumitrescu, Cristian
2015-05-12 15:32 ` Wodkowski, PawelX
2015-05-13 11:59 ` [dpdk-dev] [PATCH v2 " Pawel Wodkowski
2015-05-13 12:00 ` [dpdk-dev] [PATCH v2 1/2] cmdline: fix missing include files Pawel Wodkowski
2015-05-13 12:00 ` [dpdk-dev] [PATCH v2 2/2] cmdline: add polling mode for command line Pawel Wodkowski
2015-05-13 12:44 ` [dpdk-dev] [PATCH v2 0/2] " Dumitrescu, Cristian
2015-05-13 13:20 ` Olivier MATZ
2015-05-18 13:18 ` 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=555226FD.2060509@intel.com \
--to=pawelx.wodkowski@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=pwodkowx@stargo.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).