From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Idgar, Or" <Or.Idgar@dell.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Ravich, Leonid" <Leonid.Ravich@dell.com>
Subject: Re: CMA enhancement - non-default areas in x86
Date: Wed, 13 May 2020 08:47:55 +0200 [thread overview]
Message-ID: <20200513064755.GA763968@kroah.com> (raw)
In-Reply-To: <CH2PR19MB3767236EDC9BE964FC3AB91BFEBF0@CH2PR19MB3767.namprd19.prod.outlook.com>
On Wed, May 13, 2020 at 06:13:55AM +0000, Idgar, Or wrote:
> Hi,
> I'm working with Linux kernel on x86 and needed a way to allocate a very large contiguous memory (around 20GB) for DMA operations.
For what type of device?
> I've found out that CMA is one of the major ways to do so, but our problem is that CMA's default behavior is to create one default area from which all devices can allocate memory.
> when booting, there were some drivers that allocated memory for DMA and used CMA memory if exist. The problem is that it takes memory that we need for our device and we want to make sure this area is dedicated for our device.
>
> As I saw, the only way to reserve a dedicated area is by enabling OF_RESERVED_MEM which is available for several architectures but excluding x86 (and as far as I understand relies on device tree which is not in use with x86 or at least cannot be configured with OF_RESERVED_MEM).
>
> I really want to leverage this mechanism/API and thought about modifying the code (and hopefully merge it upstream) so multiple non-default areas will be available for x86 and with a way to consume it by mapping specific area to specific device.
>
> Is it something that will be open for merging if written properly?
We always will be glad to review patches, no need to ask us about that.
Just post them!
good luck,
greg k-h
next prev parent reply other threads:[~2020-05-13 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 6:13 Idgar, Or
2020-05-13 6:47 ` gregkh [this message]
2020-05-13 7:00 ` Idgar, Or
2020-05-13 7:14 ` gregkh
2020-05-13 8:29 ` Ravich, Leonid
2020-05-13 8:33 ` gregkh
2020-05-13 9:43 ` Ravich, Leonid
2020-05-13 10:04 ` gregkh
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=20200513064755.GA763968@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Leonid.Ravich@dell.com \
--cc=Or.Idgar@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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