From: "Butler, Siobhan A" <siobhan.a.butler@intel.com>
To: Thomas F Herbert <therbert@redhat.com>,
"Rao, Ravi" <Ravi.Rao@us.fujitsu.com>,
"O'Driscoll, Tim" <tim.o'driscoll@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] dev@DPDK Hackathon Proposal
Date: Tue, 19 May 2015 14:18:01 +0000 [thread overview]
Message-ID: <0C5AFCA4B3408848ADF2A3073F7D8CC86D60323A@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <555B440E.3040904@redhat.com>
> -----Original Message-----
> From: Thomas F Herbert [mailto:therbert@redhat.com]
> Sent: Tuesday, May 19, 2015 3:09 PM
> To: Rao, Ravi; O'Driscoll, Tim; Butler, Siobhan A; dev@dpdk.org
> Subject: Re: [dpdk-dev] dev@DPDK Hackathon Proposal
>
>
>
> On 5/19/15 9:43 AM, Rao, Ravi wrote:
> > Hi All,
> > Effort and emphasis has to be made to integrate DPDK into openstack
> components like neutron and nova so that this becomes part of std
> openstack release.
> > Currently some work was done and published as a patch to devstack's Juno
> but there are no clear path to incorporate these patches to the mainline. I
> think this would be a very good topic to cover.
> Yes
>
> Also related to this, I would hope to participate in any discussion about OVS
> acceration and vhost/guest access acceleration.
> > Regards,
> > Ravi
Thanks Thomas, Ravi - listing both your suggestions.
Siobhan
> >
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas F Herbert
> > Sent: Tuesday, May 19, 2015 8:37 AM
> > To: O'Driscoll, Tim; Butler, Siobhan A; dev@dpdk.org
> > Subject: Re: [dpdk-dev] dev@DPDK Hackathon Proposal
> >
> > On 5/19/15 8:59 AM, O'Driscoll, Tim wrote:
> >> There wasn't any public response to this but we did discuss it with several
> people separately who all thought it was a good idea. Therefore, we've
> decided to go ahead with it. Siobhan is working on the plan now and should
> be in a position to make a formal announcement in a few weeks.
> >>
> >> In the meantime, I wanted to let people know that this is going ahead so
> that you can:
> >> a) Save the date. October 8th/9th, immediately after the European
> LinuxCon, in Dublin Ireland.
> >> b) Think about topics that you'd like to see covered. We'll solicit for inputs
> when the formal announcement is made, but it's good for people to begin
> thinking about this now.
> >>
> > Tim, I for one think it is a good idea. +1 from me.
> >> We'd like this to be quite an interactive event with a lot of discussion
> rather than just presentations. We plan to have many of our key DPDK
> developers there, so it will be a great opportunity to network, discuss the
> technical challenges that you're facing and help to build a stronger DPDK
> community.
> >>
> >
> >>
> >> Tim
> >>
> >>> -----Original Message-----
> >>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Butler, Siobhan
> >>> A
> >>> Sent: Tuesday, March 31, 2015 7:19 PM
> >>> To: dev@dpdk.org
> >>> Subject: [dpdk-dev] dev@DPDK Hackathon Proposal
> >>>
> >>> Hi all,
> >>>
> >>> As a community we have virtually come together from all over the
> >>> globe, developing now our third successful open source DPDK version
> >>> with DPDK
> >>> r2.0 about to release.
> >>> It is astounding to comprehend the commitment and enthusiasm you
> >>> have all shared to bring DPDK to this point.
> >>> With growing the community of developers in mind, and strengthening
> >>> the networks and virtual collaborations that have come about, I
> >>> propose that we hold the first dev@DPDK Developer Hackathon this
> year.
> >>>
> >>> Many people will be travelling to Dublin, Ireland for LinuxCon and
> >>> CloudOpen October (5th-7th).
> >>> I propose that we hold a hands on 2 day hackathon Thursday October
> >>> 8th and Friday October 9th to coincide with this offering, in Dublin.
> >>> From a community perspective is a great opportunity to bring
> >>> together the people that make DPDK happen - the developers.
> >>> From a developer perspective it is a great opportunity to be part
> >>> of the first gathering, meet some new people, learn something new
> >>> and have a lot of fun on the way.
> >>>
> >>> At this point the agenda is open - so if you see merit in this
> >>> proposal please share your interest here so that we can gauge
> >>> attendance and gather ideas of what people would like the format to be.
> >>>
> >>> Thanks,
> >>> Siobhan
> >>> <siobhan.a.butler@intel.com>
> >
> > --
> > Thomas F Herbert
> > Principal Software Engineer
> > Red Hat
> > therbert@redhat.com
> > Office: 919-301-3295
> > Mobile: 804-741-2695
> >
>
> --
> Thomas F Herbert
> Principal Software Engineer
> Red Hat
> therbert@redhat.com
> Office: 919-301-3295
> Mobile: 804-741-2695
next prev parent reply other threads:[~2015-05-19 14:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 18:18 Butler, Siobhan A
2015-05-19 12:59 ` O'Driscoll, Tim
2015-05-19 13:36 ` Thomas F Herbert
2015-05-19 13:43 ` Rao, Ravi
2015-05-19 14:09 ` Thomas F Herbert
2015-05-19 14:18 ` Butler, Siobhan A [this message]
2015-05-19 14:22 ` Vincent JARDIN
2015-05-19 14:46 ` Thomas F Herbert
2015-05-19 16:08 ` Czesnowicz, Przemyslaw
2015-05-19 17:06 ` Rao, Ravi
2015-05-19 21:22 ` Traynor, Kevin
2015-05-19 18:18 ` Rao, Ravi
2015-05-19 14:20 ` Vincent JARDIN
2015-05-19 14:23 ` Butler, Siobhan A
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=0C5AFCA4B3408848ADF2A3073F7D8CC86D60323A@IRSMSX109.ger.corp.intel.com \
--to=siobhan.a.butler@intel.com \
--cc=Ravi.Rao@us.fujitsu.com \
--cc=dev@dpdk.org \
--cc=therbert@redhat.com \
--cc=tim.o'driscoll@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).