All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Scott Branden <scott.branden@broadcom.com>,
	Srinath Mannam <srinath.mannam@broadcom.com>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [PATCH] eal: add request to map reserved physical memory
Date: Mon, 9 Jul 2018 17:02:55 +0100	[thread overview]
Message-ID: <cca28ed7-cbb0-3a71-47f6-538418d1242b@intel.com> (raw)
In-Reply-To: <203e6af6-bff9-ca34-9b61-9f29191196fa@intel.com>

On 07-Jun-18 1:15 PM, Burakov, Anatoly wrote:
> On 06-Jun-18 1:18 AM, Scott Branden wrote:
>> Hi Anatoly,
>>
>>
>> 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?
>>>
>> Is the plan still to have a patch for 18.08?
>>
>> Thanks,
>>   Scott
>>
> Hi Scott,
> 
> The plan is still to submit an RFC during 18.08 timeframe, but since it 
> will be an ABI break, it will only be integrated in the next (18.11) 
> release.
> 
Hi Scott,

You're welcome to offer feedback on the proposal :)

http://patches.dpdk.org/project/dpdk/list/?series=453

-- 
Thanks,
Anatoly

  reply	other threads:[~2018-07-09 16:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28  4:51 [PATCH] eal: add request to map reserved physical memory 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
2018-06-06  0:18         ` Scott Branden
2018-06-07 12:15           ` Burakov, Anatoly
2018-07-09 16:02             ` Burakov, Anatoly [this message]
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=cca28ed7-cbb0-3a71-47f6-538418d1242b@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=scott.branden@broadcom.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.