From: Neil Horman <nhorman@tuxdriver.com>
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK API/ABI Stability
Date: Wed, 9 Apr 2014 14:39:52 -0400 [thread overview]
Message-ID: <20140409183952.GA16493@hmsreliant.think-freely.org> (raw)
Hey all-
I was going to include this as an addendum to the packaging thread on
this list, but I can't seem to find it in my inbox, so forgive me starting a new
one.
I wanted to broach the subject of ABI/API stability on the list here.
Given the recent great efforts to make dpdk packagable by disributions, I think
we probably need to discuss API stability in more depth and come up with a plan
to implement it. Has anyone started looking into this? If not, it seems to me
to be reasonable to start by placing a line in the sand with the functions
documented here:
http://dpdk.org/doc/api/
It seems to me we can start reviewing the API library by library, enusring only
those functions are exported, making sure the data types are appropriate for
export, and marking them with a linker script to version them appropriately.
Thoughts?
Neil
next reply other threads:[~2014-04-09 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 18:39 Neil Horman [this message]
2014-04-09 21:08 ` Stephen Hemminger
2014-04-10 10:54 ` Neil Horman
2014-04-11 17:33 ` [dpdk-dev] Poor device abstraction's Stephen Hemminger
2014-04-11 17:47 ` Neil Horman
2014-04-11 17:57 ` Venkatesan, Venky
2014-04-11 17:59 ` Neil Horman
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=20140409183952.GA16493@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.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).