DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bagh Fares <Fares.Bagh@freescale.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Community Call - ARM Support
Date: Thu, 19 Nov 2015 17:17:25 +0000	[thread overview]
Message-ID: <BLUPR0301MB165153642959F8A81CAD342B981B0@BLUPR0301MB1651.namprd03.prod.outlook.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA67463A58@IRSMSX108.ger.corp.intel.com>

Thank you Tim for addressing this. We are very interested in this activities. Our interest is having common API for our customer between various arch to ease the life of their sw developers. 
We are already writing code to contribute here.

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim
Sent: Tuesday, November 17, 2015 11:09 AM
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK Community Call - ARM Support

There's been a lot of activity on the mailing list recently on DPDK support for ARM. It's great to see the project being enhanced to embrace a new architecture.

We have seen some duplication of efforts on this, so we think it would make a good topic for a community call. This will give everybody a chance to share their plans so we can be clear on who's doing what and make sure that we avoid overlaps.

We'll host a community call on this next Tuesday (24th Nov) at 15:00-16:00 GMT. Details on the proposed agenda, the time in a couple of other timezones, and how to join the online meeting are included below.


Agenda:
ARMv7 & v8 ports:
- Summary of what's been submitted for 2.2 and what the remaining gaps are (Dave Hunt)
- Discussion on plans for further contributions in this area

External Memory Manager:
- Summary of our plans for DPDK 2.3 (Venky Venkatesan)
- Do others plan to do work in this area?

Other DPDK/ARM plans:
- Does anybody else have plans for ARM-related work in DPDK that they can share?


When: 
Tue, Nov 24, 2015 15:00 - 16:00 GMT
Tue, Nov 24, 2015 07:00 - 08:00 PST
Tue, Nov 24, 2015 10:00 - 11:00 EST
Tue, Nov 24, 2015 16:00 - 17:00 PST


Meeting Details:
You can join from your computer, tablet or smartphone: https://global.gotomeeting.com/join/535221101

You can also dial in using your phone. 

Access Code: 535-221-101 
 
Phone numbers:
United States: +1 (224) 501-3217   
Australia: +61 2 9087 3605   
Austria: +43 7 2088 1403   
Belgium: +32 (0) 28 93 7019   
Canada: +1 (647) 497-9351   
Denmark: +45 69 91 88 64   
Finland: +358 (0) 942 41 5781   
France: +33 (0) 182 880 458   
Germany: +49 (0) 692 5736 7210   
Ireland   +353 (0) 14 845 979   
Italy: +39 0 553 98 95 67   
Netherlands: +31 (0) 208 080 381   
New Zealand: +64 4 974 7214   
Norway: +47 21 03 58 98   
Spain: +34 955 32 0845   
Sweden: +46 (0) 853 527 836   
Switzerland: +41 (0) 435 0167 09   
United Kingdom: +44 (0) 330 221 0086

  parent reply	other threads:[~2015-11-19 17:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-17 17:09 O'Driscoll, Tim
2015-11-18 19:27 ` Bob Monkman
2015-11-19 11:20   ` O'Driscoll, Tim
2015-11-30 19:53     ` O'Driscoll, Tim
2015-11-19 17:17 ` Bagh Fares [this message]
2015-12-04 17:50 O'Driscoll, Tim
2015-12-08  0:55 ` Bob Monkman
2015-12-08 10:35   ` Jan Viktorin
2015-12-09 19:26 ` O'Driscoll, Tim

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=BLUPR0301MB165153642959F8A81CAD342B981B0@BLUPR0301MB1651.namprd03.prod.outlook.com \
    --to=fares.bagh@freescale.com \
    --cc=dev@dpdk.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 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).