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, 20 Mar 2020 10:34:35 +0000 [thread overview]
Message-ID: <068d657c-fc98-abdc-364e-2efe096493c9@redhat.com> (raw)
In-Reply-To: <4918e847-fc80-dc42-9b4f-c22424d1db32@redhat.com>
Next meeting April 1st 1700 UTC
Attendees: Eelco, Aaron, Marcelo, Lance, Majd, Malvika, Simon, Somnath,
David, Ajit, Ameer, Daniel, Fouad, Gaetan, Harsha, Hemal, Ian, Ilya,
Johann, Oz, Roni, Scott, Thomas, Kevin.
March 18th Minutes
- Recording is here
-- https://bluejeans.com/s/6wR3z
Agenda:
- OVS-DPDK HwOl presentation
-- Broadcom presented on their view of OVS-DPDK hardware offload
- Further meetings on OVS-DPDK HwOl
-- Next meeting in 2 weeks, can also give most of that meeting to HwOl
-- For Vxlan offload and single vs multi tables that there are
differences of opinion on the ML, Hemal and Roni/Eli said they would
have a call to try and find a consensus.
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 @ 4pm 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.
>
prev parent reply other threads:[~2020-03-20 10:34 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
2020-03-05 10:17 ` Kevin Traynor
2020-03-20 10:34 ` Kevin Traynor [this message]
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=068d657c-fc98-abdc-364e-2efe096493c9@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).