DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: "dev@openvswitch.org" <dev@openvswitch.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] OVS-DPDK public meeting
Date: Fri, 28 Feb 2020 13:53:19 +0000	[thread overview]
Message-ID: <1376910a-2d16-1275-33bd-e3227242229e@redhat.com> (raw)
In-Reply-To: <4918e847-fc80-dc42-9b4f-c22424d1db32@redhat.com>

Hi All,

There has been a request to use the next OVS-DPDK meeting (Wed March 4th
@ 17:00 UTC, call details below) to present/discuss about Hw offload
capabilities and OVS integration with DPDK rte_flow API.

Perhaps some design discussion now can save time coding/reworking later.
Would request anyone with opinion on OVS Hw offload with DPDK rte_flow
API to attend.

Talking alone can be hard, so it would be good if anyone who has some
design ideas to put a few slides together to help communicate them on
the call.

thanks,
Kevin.

On 25/07/2017 14:25, Kevin Traynor wrote:
> Hi All,
> 
> The OVS-DPDK public meetings have moved to Wednesday's at the same time.
> Everyone is welcome, it's a chance to share status/plans etc.
> 
> It's scheduled for every 2 weeks starting 26th July. Meeting time is
> currently @ 5pm UTC.
> 
> You can connect through Bluejeans or through dial in:
> 
> https://bluejeans.com/139318596
> 
> US: +1.408.740.7256
> UK: +44.203.608.5256
> Germany: +49.32.221.091256
> Ireland: +353.1.697.1256
> Other numbers at https://www.bluejeans.com/numbers
> Meeting ID: 139318596
> 
> thanks,
> Kevin.
> 


       reply	other threads:[~2020-02-28 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4918e847-fc80-dc42-9b4f-c22424d1db32@redhat.com>
2020-02-28 13:53 ` Kevin Traynor [this message]
2020-03-05 10:17 ` Kevin Traynor
2020-03-20 10:34 ` Kevin Traynor

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=1376910a-2d16-1275-33bd-e3227242229e@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dev@openvswitch.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).