DPDK patches and discussions
 help / color / mirror / Atom feed
From: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
To: Olga Shern <olgas@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Next Community Call, Tuesday 2nd December, 8:00 AM GMT
Date: Wed, 3 Dec 2014 23:07:10 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C6F06A@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <DB4PR05MB334F95CC0329D19ACDEB1FAD37B0@DB4PR05MB334.eurprd05.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 307 bytes --]

Hi Olga,

> Can you please send the presentations from last Community Call.
> We have Tetsuya's presentation,  if we can also get other presentations it will
> be great

No problem. Changchun's slides on the converged Virtio driver and Marvin's slides on the DPDK Test Suite are attached.


Tim


[-- Attachment #2: DPDK Test Suite.pdf --]
[-- Type: application/pdf, Size: 725579 bytes --]

[-- Attachment #3: Single Virtio.pdf --]
[-- Type: application/pdf, Size: 216187 bytes --]

  reply	other threads:[~2014-12-03 23:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 16:08 O'driscoll, Tim
2014-11-21 20:21 ` Neil Horman
2014-11-22 10:16   ` Butler, Siobhan A
2014-12-01  2:49 ` Tetsuya Mukawa
2014-12-01  8:35   ` Alex Markuze
2014-12-01  9:51     ` O'driscoll, Tim
2014-12-01  9:40   ` O'driscoll, Tim
2014-12-01 18:33     ` [dpdk-dev] attachment policy Thomas Monjalon
2014-12-02  2:41     ` [dpdk-dev] Next Community Call, Tuesday 2nd December, 8:00 AM GMT Tetsuya Mukawa
2014-12-03 14:55       ` Olga Shern
2014-12-03 23:07         ` O'driscoll, Tim [this message]
2014-12-04 11:30           ` Neil Horman
2014-12-04 11:36             ` Thomas Monjalon
2014-12-04 18:02               ` Neil Horman
2014-12-03 10:48 ` 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=26FA93C7ED1EAA44AB77D62FBE1D27BA54C6F06A@IRSMSX102.ger.corp.intel.com \
    --to=tim.o'driscoll@intel.com \
    --cc=dev@dpdk.org \
    --cc=olgas@mellanox.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).