DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bagh Fares <Fares.Bagh@freescale.com>
To: Dave Neary <dneary@redhat.com>,
	"CHIOSI, MARGARET T" <mc3124@att.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Pradeep Kathail \(pkathail@cisco.com\)" <pkathail@cisco.com>
Subject: Re: [dpdk-dev] Proposals from project governance meeting at DPDK Userspace (was Notes from ...)
Date: Mon, 2 Nov 2015 18:02:34 +0000	[thread overview]
Message-ID: <BLUPR0301MB1651FB584EAF082BFB3739C4982C0@BLUPR0301MB1651.namprd03.prod.outlook.com> (raw)
In-Reply-To: <5637A387.3060507@redhat.com>

Yes. Thank you. What we like is to get to a point where we discuss API and align on APIs for SOC as Margaret mention. As you know Arm has been driving ODP as the API for SOC.
What we like to do is to drive the APIs under DPDK even for Arm SOC. Long term, and based on shrinking silicon geometries, and desire to fill fabs, Intel will do more SOCs. I was SOC design manager in Intel :-)
We like to spare the customers like red hat, Cisco, and ATT the pain of supporting multiple APIs and code bases. 
So we need have a forum/place where this can be worked at . 
We are reaching out and we like to feel welcome and some love :-) 

-----Original Message-----
From: Dave Neary [mailto:dneary@redhat.com] 
Sent: Monday, November 02, 2015 11:55 AM
To: Bagh Fares-B25033 <Fares.Bagh@freescale.com>; CHIOSI, MARGARET T <mc3124@att.com>; Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org; jim.st.leger@intel.com; Pradeep Kathail (pkathail@cisco.com) <pkathail@cisco.com>
Subject: Re: [dpdk-dev] Proposals from project governance meeting at DPDK Userspace (was Notes from ...)

Hi,

On the contrary! I am aware that Freescale has been engaged for some time in DPDK. I was responding to Margaret's contention that future contributors (and she called out ARM and SOC vendors) should have a voice.

I hope that clarifies my position and meaning.

Thanks,
Dave.

On 11/02/2015 12:44 PM, Bagh Fares wrote:
> As SOC vendor we will contribute heavily to the project. Example crypto acceleration. We already contribute a lot to the linux community. 
> So not sure why the doubt about of contribution?
> 
> 
> -----Original Message-----
> From: Dave Neary [mailto:dneary@redhat.com]
> Sent: Monday, November 02, 2015 11:31 AM
> To: CHIOSI, MARGARET T <mc3124@att.com>; Stephen Hemminger 
> <stephen@networkplumber.org>; Bagh Fares-B25033 
> <Fares.Bagh@freescale.com>
> Cc: dev@dpdk.org; jim.st.leger@intel.com; Pradeep Kathail 
> (pkathail@cisco.com) <pkathail@cisco.com>
> Subject: Re: [dpdk-dev] Proposals from project governance meeting at 
> DPDK Userspace (was Notes from ...)
> 
> Hi Margaret,
> 
> On 11/02/2015 12:28 PM, CHIOSI, MARGARET T wrote:
>> I think it is very important for the first version of governance that we have ARM/SOC vendor/future contributors to be part of TSC.
>> If based on historical contribution - they will be at a disadvantage.
>> We need to have the DPDK organization support an API which supports a broader set of chips.
> 
> I think there is definitely a role for SOC vendors in the project governance, but the TSC should be representative of the technical contributors to the project, rather than an aspirational body aiming to get more people involved.
> 
> I think there is an opportunity for future contributors/users to form a powerful constituency in the project, but the TSC is not the right place for that to happen IMHO.
> 
> Thanks,
> Dave.
> 
>> -----Original Message-----
>> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
>> Sent: Monday, November 02, 2015 12:22 PM
>> To: Bagh Fares
>> Cc: dev@dpdk.org; dneary@redhat.com; jim.st.leger@intel.com; Pradeep 
>> Kathail (pkathail@cisco.com); CHIOSI, MARGARET T
>> Subject: Re: [dpdk-dev] Proposals from project governance meeting at 
>> DPDK Userspace (was Notes from ...)
>>
>> There were two outcomes.
>>
>> One was a proposal to move governance under Linux Foundation.
>>
>> The other was to have a technical steering committee.
>> It was agreed the TSC would be based on the contributors to the 
>> project, although we didn't come to a conclusion on a voting model.
>>
>>
>> I would propose that TSC should be elected at regular user summit 
>> from nominees; in a manner similar to LF Technical Advisory Board.
>>
> 
> --
> 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
> 

--
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

  reply	other threads:[~2015-11-02 18:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 18:01 Bagh Fares
2015-11-02 16:04 ` CHIOSI, MARGARET T
2015-11-02 17:21 ` Stephen Hemminger
2015-11-02 17:28   ` CHIOSI, MARGARET T
2015-11-02 17:31     ` Dave Neary
2015-11-02 17:44       ` Bagh Fares
2015-11-02 17:55         ` Dave Neary
2015-11-02 18:02           ` Bagh Fares [this message]
2015-11-02 21:44             ` O'Driscoll, Tim
2015-11-02 23:16               ` Pradeep Kathail
2015-11-03 12:43                 ` O'Driscoll, Tim
2015-11-03 13:03                   ` Thomas Monjalon
2015-11-03 22:05                   ` Bagh Fares
2015-11-03 22:47                     ` Vincent JARDIN
2015-11-03 15:17                 ` CHIOSI, MARGARET T
2015-11-03 23:35                 ` Stephen Hemminger
2015-11-04 17:02                   ` Pradeep Kathail
2015-11-02 18:01         ` Thomas Monjalon
  -- strict thread matches above, loose matches on Subject: below --
2015-10-11  0:36 [dpdk-dev] Notes from project governance meeting at DPDK Userspace Dave Neary
2015-10-12 16:45 ` [dpdk-dev] Proposals from project governance meeting at DPDK Userspace (was Notes from ...) Dave Neary

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=BLUPR0301MB1651FB584EAF082BFB3739C4982C0@BLUPR0301MB1651.namprd03.prod.outlook.com \
    --to=fares.bagh@freescale.com \
    --cc=dev@dpdk.org \
    --cc=dneary@redhat.com \
    --cc=mc3124@att.com \
    --cc=pkathail@cisco.com \
    --cc=stephen@networkplumber.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).