Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Third Annual U.S. Summit!
Date: Wed, 13 Feb 2019 22:26:17 +0000	[thread overview]
Message-ID: <353b446311ab2fed8bcc61ec3c0be67d199e0848.camel@intel.com> (raw)
In-Reply-To: 8d434f69637baa2b5a36c3413737b1737a0a2a48.camel@intel.com

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

On Mon, 2019-02-11 at 19:57 +0000, Walker, Benjamin wrote:
> As a reminder, the deadline for submitting an abstract to do a talk at the
> summit is this Friday, February 15th. Email a one or two paragraph abstract
> directly to me (benjamin.walker(a)intel.com) with your name, your contact
> information, and your company or organization.
> 
> This is a great opportunity to discuss the ways you've used SPDK or the cool
> work you plan to do in the future!

Additionally, there is an opportunity for several demos to be located
immediately outside of the main ballroom throughout the day. If anyone would
like to set up a demo of a product or proof of concept that utilizes SPDK, PMDK,
ISA-L, or DPDK please send an email with a brief description directly to me (
benjamin.walker(a)intel.com).

> 
> Thanks,
> Ben
> 
> On Tue, 2019-01-29 at 19:02 +0000, Walker, Benjamin wrote:
> > Our 3rd annual U.S. Summit is tentatively scheduled for April 16th and April
> > 17th at the Dolce Hayes Mansion in San Jose, CA (same venue as last year).
> > We
> > are working to close on the venue and will send a subsequent announcement as
> > soon as an agreement is in place. The agenda for the two day event is still
> > to
> > be determined. Sessions will include: keynote talks, what’s new, and what's
> > coming in the future. There will be technical deep dives on exciting topics
> > including NVMe-oF, Open Channel SSDs, Persistent Memory, and Networking, and
> > sessions from multiple community members.
> >  
> > At this time, we'd like to solicit talks for the summit. If your project is
> > using SPDK, PMDK, ISA-L, and/or DPDK and you'd like to give a 30 minute or
> > one
> > hour technical talk about the cool and innovative ways you're using or
> > contributing to these projects, please write a short abstract and send it
> > directly to me (benjamin.walker(a)intel.com) by February 15th. Please include
> > your
> > name, your contact information, and your company or organization. Space will
> > be
> > limited.
> >  
> > Last year’s event had 200 attendees and was not only full of great content
> > and
> > conversation, but was a ton of fun! We hope to see you there!
> > _______________________________________________
> > SPDK mailing list
> > SPDK(a)lists.01.org
> > https://lists.01.org/mailman/listinfo/spdk
> 
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk


             reply	other threads:[~2019-02-13 22:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 22:26 Walker, Benjamin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-02-11 19:57 [SPDK] Third Annual U.S. Summit! Walker, Benjamin
2019-01-29 19:02 Walker, Benjamin

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=353b446311ab2fed8bcc61ec3c0be67d199e0848.camel@intel.com \
    --to=spdk@lists.01.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