From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Olga Shern <olgas@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>,
"pawelx.wodkowski@intel.com" <pawelx.wodkowski@intel.com>,
"gowrishankar.m@linux.vnet.ibm.com"
<gowrishankar.m@linux.vnet.ibm.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
"shreyansh.jain@nxp.com" <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] [RFC] ethdev: introduce DMA memory mapping for external memory
Date: Tue, 15 Jan 2019 12:07:02 +0000 [thread overview]
Message-ID: <8c664d56-06c1-bd45-10f1-c0f57438910f@intel.com> (raw)
In-Reply-To: <DB7PR05MB4426B9C9DC6196215788BB41C3800@DB7PR05MB4426.eurprd05.prod.outlook.com>
On 14-Jan-19 6:12 AM, Shahaf Shuler wrote:
> Hi Anatoly,
>
> Any last inputs on this one? Would like to prepare a patch for 19.05 and it would much effect the design.
>
Hi Shahaf,
Unfortunately, i've been preoccupied with other stuff lately. I will
have another look at this issue over the week and come back to you.
Please feel free to ping me personally if i don't :)
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-01-15 12:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 12:41 Shahaf Shuler
2018-11-14 11:19 ` Burakov, Anatoly
2018-11-14 14:53 ` Shahaf Shuler
2018-11-14 17:06 ` Burakov, Anatoly
2018-11-15 9:46 ` Shahaf Shuler
2018-11-15 10:59 ` Burakov, Anatoly
2018-11-19 11:20 ` Shahaf Shuler
2018-11-19 17:18 ` Burakov, Anatoly
[not found] ` <DB7PR05MB442643DFD33B71797CD34B5EC3D90@DB7PR05MB4426.eurprd05.prod.outlook.com>
2018-11-20 10:55 ` Burakov, Anatoly
2018-11-22 10:06 ` Shahaf Shuler
2018-11-22 10:41 ` Burakov, Anatoly
2018-11-22 11:31 ` Shahaf Shuler
2018-11-22 11:34 ` Burakov, Anatoly
2019-01-14 6:12 ` Shahaf Shuler
2019-01-15 12:07 ` Burakov, Anatoly [this message]
2019-01-16 11:04 ` Shahaf Shuler
2018-11-19 17:04 ` Stephen Hemminger
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=8c664d56-06c1-bd45-10f1-c0f57438910f@intel.com \
--to=anatoly.burakov@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gowrishankar.m@linux.vnet.ibm.com \
--cc=olgas@mellanox.com \
--cc=pawelx.wodkowski@intel.com \
--cc=shahafs@mellanox.com \
--cc=shreyansh.jain@nxp.com \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.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).