DPDK patches and discussions
 help / color / mirror / Atom feed
From: Don Wallwork <donw@xsightlabs.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [RFC] EAL: legacy memory fixed address translations
Date: Wed, 27 Jul 2022 15:27:06 -0400	[thread overview]
Message-ID: <9b885e57-0ed9-ec28-314e-04397892027c@xsightlabs.com> (raw)
In-Reply-To: <20220727121024.29829f3e@hermes.local>

On 7/27/2022 3:12 PM, Stephen Hemminger wrote:
> On Wed, 27 Jul 2022 13:20:22 -0400
> Don Wallwork <donw@xsightlabs.com> wrote:
>
>>> When drivers need to process a large number of memory blocks,
>>> these are typically packets in the form of mbufs,
>>> which already have IOVA attached, so there is no translation.
>>> Does translation of mbuf VA to PA with the proposed method
>>> show significant improvement over reading mbuf->iova?
>> This proposal does not relate to mbufs.  As you say, there is
>> already an efficient VA to PA mechanism in place for those.
>
> If the only user of this would be your out of tree code,
> then it would never get tested by normal process.
> Therefore it would be regularly broken by other changes.

While we're not yet ready to upstream our drivers, we are actively
working to get our code ready for that.  It is expected that other
devices may be able to take advantage of this capability.  In the
meantime, tests could be added to prevent such breakage.

  reply	other threads:[~2022-07-27 19:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26 18:18 RFC: EAL " Don Wallwork
2022-07-26 18:33 ` [RFC] EAL: " Don Wallwork
2022-07-26 19:59   ` Dmitry Kozlyuk
2022-07-27 17:20     ` Don Wallwork
2022-07-27 19:12       ` Stephen Hemminger
2022-07-27 19:27         ` Don Wallwork [this message]
2022-07-27 20:36       ` Dmitry Kozlyuk
2022-07-27 21:43         ` Don Wallwork
2022-07-28  7:25           ` Dmitry Kozlyuk
2022-07-28 11:29             ` Morten Brørup
2022-07-28 14:46               ` Don Wallwork
2022-07-28 15:41                 ` Don Wallwork
2022-07-28 16:33                   ` Dmitry Kozlyuk

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=9b885e57-0ed9-ec28-314e-04397892027c@xsightlabs.com \
    --to=donw@xsightlabs.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=stephen@networkplumber.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).