From: Scott Branden <scott.branden@broadcom.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
Srinath Mannam <srinath.mannam@broadcom.com>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: add request to map reserved physical memory
Date: Fri, 27 Apr 2018 10:09:49 -0700 [thread overview]
Message-ID: <2d811eaa-a434-a923-abc8-25b9f450be9f@broadcom.com> (raw)
In-Reply-To: <76474922-b2ad-dfcd-d62b-f605ec47d2e6@intel.com>
On 18-04-27 09:49 AM, Burakov, Anatoly wrote:
> On 27-Apr-18 5:30 PM, Scott Branden wrote:
>> Hi Anatoly,
>>
>> We'd appreciate your input so we can come to a solution of supporting
>> the necessary memory allocations?
>>
>
> Hi Scott,
>
> I'm currently starting to work on a prototype that will be at least
> RFC'd (if not v1'd) during 18.08 timeframe. Basically, the idea is to
> create/destroy named malloc heaps dynamically, and allow user to
> request memory from them. You may then mmap() whatever you want and
> create a malloc heap out of it.
>
> Does that sound reasonable?
Hi Anatoly,
We have a solution right now that requires a kernel driver to allocate
large contiguous memory and the DPDK changes in the patch. We would like
to come to a common upstreamed solution as soon as possible. So please
send out the patch as soon as you can and we can test/comment on it. I
would hope this is a simple addition and shouldn't take long to come to
an acceptable implementation. We need this change for DPDK to operate
on our devices.
Thanks,
Scott
next prev parent reply other threads:[~2018-04-27 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 4:51 Ajit Khaparde
2018-04-12 14:35 ` Burakov, Anatoly
2018-04-23 9:23 ` Srinath Mannam
2018-04-27 16:30 ` Scott Branden
2018-04-27 16:49 ` Burakov, Anatoly
2018-04-27 17:09 ` Scott Branden [this message]
2018-06-06 0:18 ` Scott Branden
2018-06-07 12:15 ` Burakov, Anatoly
2018-07-09 16:02 ` Burakov, Anatoly
2018-07-09 16:12 ` Srinath Mannam
2018-07-09 20:44 ` Scott Branden
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=2d811eaa-a434-a923-abc8-25b9f450be9f@broadcom.com \
--to=scott.branden@broadcom.com \
--cc=ajit.khaparde@broadcom.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=srinath.mannam@broadcom.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).