From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Rajesh Ravi <rajesh.ravi@broadcom.com>
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>,
dev@dpdk.org,
Jonathan Richardson <jonathan.richardson@broadcom.com>,
Scott Branden <scott.branden@broadcom.com>,
Vikram Mysore Prakash <vikram.prakash@broadcom.com>,
Srinath Mannam <srinath.mannam@broadcom.com>
Subject: Re: [dpdk-dev] [PATCH] eal: add option --iso-cmem for external custom memory
Date: Tue, 5 Nov 2019 17:13:42 +0000 [thread overview]
Message-ID: <f8d53381-9d72-fade-d969-3a9ecb7a6e53@intel.com> (raw)
In-Reply-To: <e8e00359-1b1d-26d0-5f56-02599bf921c3@intel.com>
On 05-Nov-19 3:18 PM, Burakov, Anatoly wrote:
> On 05-Nov-19 2:10 PM, Rajesh Ravi wrote:
>> Thanks a lot Anatoly.
>> Will the same solution work with DPDK 19.02 as well? We 're actually
>> using DPDK 19.02 for memory allocations for SPDK 19.07.
>> DPDK 19.11 may not be supported by SPDK 19.07 we 're currently using.
>>
>> I 'll definitely test if the patch works with DPDK 19.02
>>
>> Thanks again for your time and help.
>>
>> Regards,
>> Rajesh
>
> Hi Rajesh,
>
> Please test the patch [1] and see if it works for you. The patch is not
> intended for 19.02 (in fact, 19.02 is not even supported any more), but
> it may still apply. In the meantime, i'm working on a different patch
> for 18.11, that will achieve the same thing using different means.
>
> [1] http://patches.dpdk.org/patch/62468/
>
The following is an alternative implementation that is based off 18.11:
http://patches.dpdk.org/patch/62486/
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-11-05 17:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 5:30 [dpdk-dev] [PATCH] eal: add option --iso-cmem for external custom memory Ajit Khaparde
2019-10-17 15:45 ` Burakov, Anatoly
2019-10-18 10:54 ` Rajesh Ravi
2019-10-18 16:53 ` Burakov, Anatoly
2019-10-21 15:46 ` Rajesh Ravi
2019-10-22 7:56 ` Rajesh Ravi
2019-10-24 11:43 ` Burakov, Anatoly
2019-10-25 12:53 ` Rajesh Ravi
2019-10-25 15:02 ` Burakov, Anatoly
2019-10-30 19:50 ` Rajesh Ravi
2019-11-04 10:25 ` Burakov, Anatoly
2019-11-05 11:41 ` Burakov, Anatoly
2019-11-05 14:10 ` Rajesh Ravi
2019-11-05 15:18 ` Burakov, Anatoly
2019-11-05 17:13 ` Burakov, Anatoly [this message]
2019-11-06 13:55 ` David Marchand
2019-11-07 15:51 ` David Marchand
2019-11-07 16:16 ` Rajesh Ravi
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=f8d53381-9d72-fade-d969-3a9ecb7a6e53@intel.com \
--to=anatoly.burakov@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=jonathan.richardson@broadcom.com \
--cc=rajesh.ravi@broadcom.com \
--cc=scott.branden@broadcom.com \
--cc=srinath.mannam@broadcom.com \
--cc=vikram.prakash@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).