DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK Community Call - Software QoS
Date: Fri, 24 Apr 2015 12:17:27 +0200	[thread overview]
Message-ID: <3049764.NGfj07NxoY@xps13> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D89126323586B3@IRSMSX108.ger.corp.intel.com>

2015-04-24 09:14, Dumitrescu, Cristian:
> Hi Tim,
> 
> Thank you for your help in recording this readout!
> The slides that you attached to the email are dropped by the dpdk.org email server.

No, they are not dropped:
	http://dpdk.org/ml/archives/dev/2015-April/016842.html
	http://dpdk.org/ml/archives/dev/attachments/20150423/17a4d8de/attachment-0001.pdf

> Thomas,
> 
> I suggest we setup a page on dpdk.org to keep track of all the community readouts,
> we can store there the slides and a link to the Youtube video, when available.
> What do you think?

I think first that we must focus on having a good and up-to-date official documentation.

The document you attached and the audio explanation are a snapshot which can be
referenced in a page dedicated to not updated or external documents. So it will
be important to put a date on these entries and sort them by date.

I suggest to create a page "discussion supports" which will be linked from
http://dpdk.org/doc in the "Archives" section.

  reply	other threads:[~2015-04-24 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-01 15:41 O'driscoll, Tim
2015-04-01 21:05 ` O'driscoll, Tim
2015-04-23 11:23 ` O'Driscoll, Tim
2015-04-24  9:14   ` Dumitrescu, Cristian
2015-04-24 10:17     ` Thomas Monjalon [this message]
2015-04-24 10:23       ` Dumitrescu, Cristian

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=3049764.NGfj07NxoY@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.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).