From: Yuanhan Liu <yliu@fridaylinux.org>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
dev@dpdk.org, Tetsuya Mukawa <mtetsuyah@gmail.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] vhost: introduce rte_vhost_vring_call()
Date: Mon, 8 Jan 2018 21:46:22 +0800 [thread overview]
Message-ID: <20180108134622.GQ8818@yliu-mob> (raw)
In-Reply-To: <698ad293-18d8-30c6-eae7-df5e1bd2b64c@redhat.com>
On Wed, Jan 03, 2018 at 09:17:32AM +0100, Maxime Coquelin wrote:
> >>Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> >
> > From 3.2. Managing ABI updates, General Guidelines:
> >
> > New APIs will be marked as experimental for at least one release to
> > allow any issues found by users of the new API to be fixed quickly.
> >
> >http://dpdk.org/doc/guides/contributing/versioning.html
> >
> >I'm new to DPDK so I followed this guideline strictly and expect the
> >maintainers to mark the API stable at some point in the future when they
> >are happy with it. Maybe this guideline isn't followed strictly for
> >librte_vhost?
>
> Thanks for the pointer, it seems it is not strictly followed for
> librte_vhost & other libs. Let's keep it experimental for the coming
> release.
IIRC, it's a new guideline added recently (people were talking about
that in last year's DPDK user event after all).
And my understanding is, for a new (big set of) APIs, it's good to
make them experimental, as normally, it's not an easy task to make
a big stuff right in one time.
For this one, which is simple and straightforward, I don't see a
strong need to mark it as experimental.
Thus I have removed it (while apply). If anyone has objections,
let me know.
Thanks.
--yliu
prev parent reply other threads:[~2018-01-08 13:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-02 9:31 Stefan Hajnoczi
2018-01-02 9:31 ` [dpdk-dev] [PATCH v2 1/2] vhost: add vhost_vring_call() helper Stefan Hajnoczi
2018-01-02 9:31 ` [dpdk-dev] [PATCH v2 2/2] vhost: introduce rte_vhost_vring_call() Stefan Hajnoczi
2018-01-02 10:27 ` [dpdk-dev] [PATCH v2 0/2] " Maxime Coquelin
[not found] ` <20180102181141.GC22252@stefanha-x1.localdomain>
2018-01-03 8:17 ` Maxime Coquelin
2018-01-08 13:46 ` Yuanhan Liu [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=20180108134622.GQ8818@yliu-mob \
--to=yliu@fridaylinux.org \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=mtetsuyah@gmail.com \
--cc=stefanha@redhat.com \
--cc=thomas@monjalon.net \
/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).