DPDK patches and discussions
 help / color / mirror / Atom feed
From: Don Wallwork <donw@xsightlabs.com>
To: "Morten Brørup" <mb@smartsharesystems.com>,
	"Dmitry Kozlyuk" <dmitry.kozliuk@gmail.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [RFC] EAL: legacy memory fixed address translations
Date: Thu, 28 Jul 2022 11:41:19 -0400	[thread overview]
Message-ID: <c7d7cf6e-f566-bb8e-5da8-d2030eb0b7e6@xsightlabs.com> (raw)
In-Reply-To: <7a030fd7-65ab-787d-60df-1eae8d5b6f06@xsightlabs.com>

[-- Attachment #1: Type: text/plain, Size: 719 bytes --]

On 7/28/2022 10:46 AM, Don Wallwork wrote:
>>>> Let me try to give a trivial example of how it would work
>>>> to make sure we're on the same page and then we can get
>>>> back to details..
>>> Thanks you, Don.
>>> Now it's perfectly clear what EAL should do and we can discuss API.
>> I think this RFC is an excellent proposal!
>
> Thanks Morten and Dmitry. Great to hear that.  When we have a
> patch ready, will post on the list.

One question I'd like to ask before diving into the code is: if there
is general application for this feature, is this something the memory
system maintainers would prefer to implement or is it preferred that
we provide a patch and get guidance from maintainers?  Either way
is fine.

[-- Attachment #2: Type: text/html, Size: 1439 bytes --]

  reply	other threads:[~2022-07-28 15:41 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
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 [this message]
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=c7d7cf6e-f566-bb8e-5da8-d2030eb0b7e6@xsightlabs.com \
    --to=donw@xsightlabs.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=mb@smartsharesystems.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).