From: Li Feng <fengli@smartx.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Feng Li <lifeng1519@gmail.com>, dev <dev@dpdk.org>,
Kyle Zhang <kyle@smartx.com>, Yang Fan <fanyang@smartx.com>
Subject: [dpdk-dev] [PATCH] librte_eal: add APIs to speedup virt2iova/phys
Date: Mon, 29 Mar 2021 14:26:04 +0800 [thread overview]
Message-ID: <CAHckoCyWhU7QnxJpezE7kksiQHkAooYTVx+7h-Zdp=-O5EjLZw@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8wZ17htmb9a9SsQNd1gDCF7FGt90eqXyAaQyEumUuKD+A@mail.gmail.com>
Hi david,
Sorry for late response.
I just see your mail on my trip.
I will update this patch, if anyone has interest in this feature.
Currently it's in my own repo.
在 2021年3月25日星期四，David Marchand <david.marchand@redhat.com> 写道：
> Hello,
>
> On Mon, Apr 20, 2020 at 4:13 PM Li Feng <fengli@smartx.com> wrote:
> >
> > Cool, thank you, Anatoly and Kozlyuk.
> >
> > I haven't found how Windows implements the rte_mem_virt2phy.
> >
> > Using an opaque structure pointer as the first argument is a good idea.
>
> I pinged about this patch status 6 months ago but got no reply.
> Trying again in public.
>
> From the thread, I understand that at best it would have to be done
> differently.
>
>
> --
> David Marchand
>
>
--
Thanks,
Feng Li
next prev parent reply other threads:[~2021-03-29 6:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 11:09 Li Feng
2020-04-20 12:16 ` Burakov, Anatoly
2020-04-20 13:07 ` Dmitry Kozlyuk
2020-04-20 14:13 ` Li Feng
2021-03-25 13:32 ` David Marchand
2021-03-29 6:26 ` Li Feng [this message]
2021-04-01 10:38 ` Burakov, Anatoly
2021-04-06 10:40 ` Feng Li
2021-04-06 11:23 ` David Marchand
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='CAHckoCyWhU7QnxJpezE7kksiQHkAooYTVx+7h-Zdp=-O5EjLZw@mail.gmail.com' \
--to=fengli@smartx.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=fanyang@smartx.com \
--cc=kyle@smartx.com \
--cc=lifeng1519@gmail.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).