From: Bob Monkman <Bob.Monkman@arm.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Prasun.Kapoor@caviumnetworks.com"
<Prasun.Kapoor@caviumnetworks.com>,
"Liu, Kin-Yip" <Kin-Yip.Liu@caviumnetworks.com>
Subject: Re: [dpdk-dev] DPDK Community Call - ARM Support
Date: Tue, 8 Dec 2015 00:55:27 +0000 [thread overview]
Message-ID: <VI1PR08MB05760E84EA92429C4A80B96BEF080@VI1PR08MB0576.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA67474276@IRSMSX108.ger.corp.intel.com>
Tim,
Yes, and I have been meaning to ask Venky to send out the presentation again. This was asked at the meeting and it fell through the cracks. I had wanted to ping some of the ARM SoC folks to read it and come prepared to discuss. As it stands, I will send a note anyways and see if I can get some interested stakeholders there. I recall some of the Cavium folks were online last time.
Regards,
Bob
Robert (Bob) Monkman
Enterprise Segment Marketing Manager
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of O'Driscoll, Tim
Sent: Friday, December 04, 2015 9:51 AM
To: dev@dpdk.org
Subject: [dpdk-dev] DPDK Community Call - ARM Support
I missed Tuesday's call as I was travelling, but I believe one of the outcomes was to hold another call at the same time on Tuesday 8th to further discuss the External Mempool Manager. Here are the details:
When:
Tue, Dec 8, 2015 15:00 - 16:00 GMT
Tue, Dec 8, 2015 07:00 - 08:00 PST
Tue, Dec 8, 2015 10:00 - 11:00 EST
Tue, Dec 8, 2015 16:00 - 17:00 CET
How to join:
You can join from your computer, tablet or smartphone: https://global.gotomeeting.com/join/704010829
You can also dial in using your phone.
Access Code: 704-010-829
Phone numbers
United States : +1 (786) 358-5410
Australia : +61 2 9087 3604
Austria : +43 7 2088 0034
Belgium : +32 (0) 28 93 7018
Canada : +1 (647) 497-9350
Denmark : +45 69 91 88 62
Finland : +358 (0) 942 41 5778
France : +33 (0) 182 880 456
Germany : +49 (0) 692 5736 7211
Ireland : +353 (0) 15 290 180
Italy : +39 0 699 36 98 80
Netherlands : +31 (0) 208 908 267
New Zealand : +64 9 442 7358
Norway : +47 21 54 32 44
Spain : +34 911 23 0850
Sweden : +46 (0) 853 527 835
Switzerland : +41 (0) 435 0006 96
United Kingdom : +44 (0) 20 3713 5028
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
next prev parent reply other threads:[~2015-12-08 0:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 17:50 O'Driscoll, Tim
2015-12-08 0:55 ` Bob Monkman [this message]
2015-12-08 10:35 ` Jan Viktorin
2015-12-09 19:26 ` O'Driscoll, Tim
-- strict thread matches above, loose matches on Subject: below --
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
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=VI1PR08MB05760E84EA92429C4A80B96BEF080@VI1PR08MB0576.eurprd08.prod.outlook.com \
--to=bob.monkman@arm.com \
--cc=Kin-Yip.Liu@caviumnetworks.com \
--cc=Prasun.Kapoor@caviumnetworks.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).