All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Subject: Re: 17.02 Roadmap
Date: Fri, 14 Oct 2016 22:18:40 +0200	[thread overview]
Message-ID: <1558423.Do1gQogAzQ@xps13> (raw)
In-Reply-To: <20161014102945.641b866e@xeon-e3>

2016-10-14 10:29, Stephen Hemminger:
> It seems like a lot of these feature are focused too narrowly on exposing
> features that exist on specific Intel hardware. The concept of a general
> purpose Dataplane Development Kit is that applications can be written that
> have a generic API (like any operating system) that will run on a wide
> variety of hardware.  This concept seems to getting lost as the DPDK is
> becoming more of a platform for exposing what ever cool hardware features
> exist.
> 
> I would propose that no new feature be allowed in the DPDK unless it
> can be supported on all device types. Yes that means you have to build
> and test software emulation layers for all other devices. The current
> model is more of a hardware test bed.

Thanks for the reminder Stephen. It is good goal.
I think the software emulation idea is finding its way.
About forbidding new hardware feature without emulation support,
it has to be discussed.

  reply	other threads:[~2016-10-14 20:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 16:13 17.02 Roadmap O'Driscoll, Tim
2016-10-10 20:42 ` Thomas Monjalon
2016-10-11  5:32   ` Yuanhan Liu
2016-10-11  9:09   ` O'Driscoll, Tim
2016-10-11 10:25   ` Pattan, Reshma
2016-10-11 22:36   ` De Lara Guarch, Pablo
2016-10-13  3:15   ` Tan, Jianfeng
2016-10-13 14:18   ` Hunt, David
2016-10-13 14:39     ` Thomas Monjalon
2016-10-14 17:29 ` Stephen Hemminger
2016-10-14 20:18   ` Thomas Monjalon [this message]
2016-10-16 20:21     ` O'Driscoll, Tim
  -- strict thread matches above, loose matches on Subject: below --
2016-08-31 10:31 O'Driscoll, Tim
2016-08-31 12:07 ` 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=1558423.Do1gQogAzQ@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=tim.odriscoll@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 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.