DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dave Neary <dneary@redhat.com>
To: Panu Matilainen <pmatilai@redhat.com>,
	Yuanhan Liu <yuanhan.liu@linux.intel.com>,
	Arnon Warshavsky <arnon@qwilt.com>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>,
	Thomas Monjalon <thomas.monjalon@6wind.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK namespace
Date: Wed, 6 Apr 2016 16:21:44 -0400	[thread overview]
Message-ID: <57056FD8.70602@redhat.com> (raw)
In-Reply-To: <5704FC10.8020405@redhat.com>

Hi,

On 04/06/2016 08:07 AM, Panu Matilainen wrote:
>> +1: it's a bit weird to keep both, especially for a long while, that
>> every time we turn a rte_ prefix to dpdk_ prefix, we break applications.
>> Instead of breaking applications many times, I'd prefer to break once.
>> Therefore, applications could do a simple global rte_ -> dpdk_
>> substitute:
>> it doesn't sound that painful then.
> 
> I concur. If (and I think that should be a pretty big IF) the prefix is
> to be changed then its better done in one fast sweep than gradually.
> 
> Gratuitious (or nearly so) change is always extremely annoying, and the
> longer it takes the more painful it is. Application developers wont much
> care what the prefix is as long as its consistent, but if they're forced
> to track prefix changes across several releases with different libraries
> moving at different pace, they WILL be calling for bloody murder :)

How about the idea of creating (at switch over time) an optionally
installable dpdk_compat package that just has a list of #defines for the
old symbols pointing them at the new symbols? That would also allow
people with old applications to update DPDK without having to modify
their applications.

Thanks,
Dave.

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338

  parent reply	other threads:[~2016-04-06 20:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 13:56 Thomas Monjalon
2016-04-05 14:13 ` Trahe, Fiona
2016-04-05 14:31   ` Trahe, Fiona
2016-04-05 14:31   ` Arnon Warshavsky
2016-04-06  5:26     ` Yuanhan Liu
2016-04-06 12:07       ` Panu Matilainen
2016-04-06 12:34         ` Ananyev, Konstantin
2016-04-06 14:36         ` Wiles, Keith
2016-04-06 20:21         ` Dave Neary [this message]
2016-04-07  8:22           ` Marc
2016-04-11 16:10         ` Don Provan
2016-04-11 16:28           ` Thomas Monjalon
2016-04-06 12:41       ` Jay Rolette
2016-04-06 12:51         ` Mcnamara, John
2016-04-07  9:18 ` Thomas Monjalon
2016-04-07  9:33   ` Panu Matilainen
2016-04-07 10:16     ` Marc Sune
2016-04-07 11:51       ` [dpdk-dev] On DPDK ABI policy Panu Matilainen
2016-04-07 21:52         ` Matthew Hall
2016-04-08  8:29           ` Marc Sune
2016-04-08  8:47         ` Marc Sune
2016-04-07 21:48       ` [dpdk-dev] DPDK namespace Matthew Hall
2016-04-07 22:01   ` 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=57056FD8.70602@redhat.com \
    --to=dneary@redhat.com \
    --cc=arnon@qwilt.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=pmatilai@redhat.com \
    --cc=thomas.monjalon@6wind.com \
    --cc=yuanhan.liu@linux.intel.com \
    /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).