From: Thomas Monjalon <thomas@monjalon.net>
To: "Stokes, Ian" <ian.stokes@intel.com>
Cc: Ilya Maximets <i.maximets@redhat.com>,
"Maxime Coquelin (maxime.coquelin@redhat.com)"
<maxime.coquelin@redhat.com>,
"Pai G, Sunil" <sunil.pai.g@intel.com>,
"Hu, Jiayu" <jiayu.hu@intel.com>,
"ovs-dev@openvswitch.org" <ovs-dev@openvswitch.org>,
"dev@dpdk.org" <dev@dpdk.org>,
Kevin Traynor <ktraynor@redhat.com>,
Flavio Leitner <fbl@redhat.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
"Ferriter, Cian" <cian.ferriter@intel.com>,
"mcoqueli@redhat.com" <mcoqueli@redhat.com>,
"fleitner@redhat.com" <fleitner@redhat.com>
Subject: Re: OVS DPDK DSA Architecture/Design Discussion
Date: Tue, 15 Mar 2022 12:00:20 +0100 [thread overview]
Message-ID: <2144208.72vocr9iq0@thomas> (raw)
In-Reply-To: <55227b9e9dcf4562a4dae8ef4c2938bf@intel.com>
15/03/2022 11:27, Stokes, Ian:
> Hi All,
>
> We'd like to put a public meeting in place for the stakeholders
> of DPDK and OVS to discuss the next steps and design of
> the DSA library along with its integration in OVS.
There is no DSA library.
Do you mean the IOAT driver in DPDK for the DMA library?
If it is just for discussing the Intel driver, no way I attend.
And even if it is for discussing the DMA library integration,
I don't understand why the DPDK community is required.
If there is an issue with the library API, please tell it.
We need email discussions, not meeting request sent few hours in advance.
Ian, I know you are not a beginner in the community, what happens?
next prev parent reply other threads:[~2022-03-15 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 10:27 Stokes, Ian
2022-03-15 11:00 ` Thomas Monjalon [this message]
2022-03-15 11:14 ` Stokes, Ian
2022-03-15 11:34 ` Thomas Monjalon
2022-03-15 13:20 ` Stokes, Ian
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=2144208.72vocr9iq0@thomas \
--to=thomas@monjalon.net \
--cc=cian.ferriter@intel.com \
--cc=dev@dpdk.org \
--cc=fbl@redhat.com \
--cc=fleitner@redhat.com \
--cc=harry.van.haaren@intel.com \
--cc=i.maximets@redhat.com \
--cc=ian.stokes@intel.com \
--cc=jiayu.hu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mcoqueli@redhat.com \
--cc=ovs-dev@openvswitch.org \
--cc=sunil.pai.g@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).