From: "Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Anoob Joseph <anoobj@marvell.com>,
Nikhil Rao <nikhil.rao@intel.com>,
Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
Abhinandan Gujjar <abhinandan.gujjar@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: Narayana Prasad Raju Athreya <pathreya@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Lukas Bartosik <lbartosik@marvell.com>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Nipun Gupta <nipun.gupta@nxp.com>,
Harry van Haaren <harry.van.haaren@intel.com>,
Liang Ma <liang.j.ma@intel.com>,
"techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 00/39] adding eventmode helper library
Date: Fri, 28 Jun 2019 10:02:45 +0200 [thread overview]
Message-ID: <848c585a-9f62-60eb-5069-862295551d2d@ericsson.com> (raw)
In-Reply-To: <BYAPR18MB2424BF86BE170483BC07D3CCC8FC0@BYAPR18MB2424.namprd18.prod.outlook.com>
On 2019-06-28 05:37, Jerin Jacob Kollanukkaran wrote:
>>>
>>> I have only concern about moving this as library inside eventdev that
>>> till we have mature version of helper library the eventdev library ABI
>>> will not stable(i.e .so file version needs to be incremented as when a
>>> change needed). Which align with Mattias thoughts for some other
>>> reason:. How about moving this code to
>>> 1) example/common or
>>> 2) to specific application itself, once at least two applications
>>> starts using it then move to Eventdev library.
>>>
>>> Thoughts?
>>
>> [Anoob] Either location is not a problem if there is a consensus. Earlier the
>> suggestion was to move it to library (when the patch was submitted with
>> changes added in app).
>
>
> If there NO objections then lets move to example/common.
>
That sounds like a good idea to me.
I wish I had more time to devote to eventmode, so I could be more
constructive than basically just saying "it's a hard problem" and "the
proposed solution seems not generic-enough by far" - but I don't at the
moment.
next prev parent reply other threads:[~2019-06-28 8:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 10:33 Jerin Jacob Kollanukkaran
2019-06-27 5:28 ` Anoob Joseph
2019-06-28 3:37 ` Jerin Jacob Kollanukkaran
2019-06-28 8:02 ` Mattias Rönnblom [this message]
2019-06-28 8:40 ` Thomas Monjalon
2019-06-28 9:07 ` Mattias Rönnblom
2019-06-28 11:34 ` [dpdk-dev] [EXT] " Anoob Joseph
2019-07-02 14:17 ` Anoob Joseph
2019-07-02 14:26 ` Jerin Jacob Kollanukkaran
2019-07-02 14:49 ` Bruce Richardson
2019-07-02 14:57 ` Thomas Monjalon
2019-07-02 16:18 ` Anoob Joseph
2019-07-02 17:38 ` Mattias Rönnblom
2019-07-03 1:35 ` Anoob Joseph
2019-07-03 8:51 ` Thomas Monjalon
2019-07-03 9:37 ` Anoob Joseph
2019-07-03 16:30 ` Thomas Monjalon
2019-07-04 3:34 ` Anoob Joseph
-- strict thread matches above, loose matches on Subject: below --
2019-06-03 17:32 [dpdk-dev] " Anoob Joseph
2019-06-07 9:48 ` Jerin Jacob Kollanukkaran
2019-06-11 10:44 ` Mattias Rönnblom
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=848c585a-9f62-60eb-5069-862295551d2d@ericsson.com \
--to=mattias.ronnblom@ericsson.com \
--cc=abhinandan.gujjar@intel.com \
--cc=anoobj@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=lbartosik@marvell.com \
--cc=liang.j.ma@intel.com \
--cc=nikhil.rao@intel.com \
--cc=nipun.gupta@nxp.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=pathreya@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=techboard@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).