From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] SPDK Dependencies
Date: Thu, 27 Apr 2017 21:10:27 +0000 [thread overview]
Message-ID: <1493327426.6290.23.camel@intel.com> (raw)
In-Reply-To: be40c3b4-1b8f-55b0-0ee2-17d0def63677@oracle.com
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Thu, 2017-04-27 at 11:06 +0530, Ranjit Noronha wrote:
>
> I think there was also a proposal to consolidate/refactor/reduce the env API.
> Where are we with that proposal? Is it an activity that will start once the
> current SPDK/DPDK separation completes or do we plan to do it concurrently. It
> would be nice to say we are "done" with the API changes at some point, in a
> sense freezing the API, unless there is a bug that needs fixing, or additions
> that came out of unforeseen requirements.
> This allows other environments a stable interface that may be implemented
> without too much churn and rebase anxiety.
> thanks,
> --ranjit
This is an ongoing background activity that will continue for some time. We'll
make sure to keep the env API as stable as possible once DPDK is fully
abstracted and strive to only do wholesale removal of functions once we don't
need them anymore. Removing a function from the API isn't particularly
disruptive in my opinion, whereas changing an API definitely is.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3274 bytes --]
next reply other threads:[~2017-04-27 21:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 21:10 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-05-05 10:08 [SPDK] SPDK Dependencies John Meneghini
2017-05-03 2:23 John Meneghini
2017-04-29 11:46 Meneghini, John
2017-04-29 11:38 Rodriguez, Edwin
2017-04-27 5:36 Ranjit Noronha
2017-04-26 22:09 Walker, Benjamin
2017-04-17 18:55 Walker, Benjamin
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=1493327426.6290.23.camel@intel.com \
--to=spdk@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.