From: Michal Nazarewicz <mina86@mina86.com>
To: Michal Hocko <mhocko@kernel.org>, Vlastimil Babka <vbabka@suse.cz>
Cc: "Robin H. Johnson" <robbat2@gentoo.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
dri-devel@lists.freedesktop.org, Joonsoo Kim <js1304@gmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>
Subject: Re: drm/radeon spamming alloc_contig_range: [xxx, yyy) PFNs busy busy
Date: Thu, 01 Dec 2016 17:03:52 +0100 [thread overview]
Message-ID: <xa1t37i7ocuv.fsf@mina86.com> (raw)
In-Reply-To: <20161201141125.GB20966@dhcp22.suse.cz>
On Thu, Dec 01 2016, Michal Hocko wrote:
> Let's also CC Marek
>
> On Thu 01-12-16 08:43:40, Vlastimil Babka wrote:
>> On 12/01/2016 08:21 AM, Michal Hocko wrote:
>> > Forgot to CC Joonsoo. The email thread starts more or less here
>> > http://lkml.kernel.org/r/20161130092239.GD18437@dhcp22.suse.cz
>> >
>> > On Thu 01-12-16 08:15:07, Michal Hocko wrote:
>> > > On Wed 30-11-16 20:19:03, Robin H. Johnson wrote:
>> > > [...]
>> > > > alloc_contig_range: [83f2a3, 83f2a4) PFNs busy
>> > >
>> > > Huh, do I get it right that the request was for a _single_ page? Why do
>> > > we need CMA for that?
>>
>> Ugh, good point. I assumed that was just the PFNs that it failed to migrate
>> away, but it seems that's indeed the whole requested range. Yeah sounds some
>> part of the dma-cma chain could be smarter and attempt CMA only for e.g.
>> costly orders.
>
> Is there any reason why the DMA api doesn't try the page allocator first
> before falling back to the CMA? I simply have a hard time to see why the
> CMA should be used (and fragment) for small requests size.
There actually may be reasons to always go with CMA even if small
regions are requested. CMA areas may be defined to map to particular
physical addresses and given device may require allocations from those
addresses. This may be more than just a matter of DMA address space.
I cannot give you specific examples though and I might be talking
nonsense.
> --
> Michal Hocko
> SUSE Labs
--
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-12-01 16:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <robbat2-20161129T223723-754929513Z@orbis-terrarum.net>
2016-11-30 9:22 ` PROBLEM-PERSISTS: dmesg spam: alloc_contig_range: [XX, YY) PFNs busy Michal Hocko
2016-11-30 13:08 ` Michal Nazarewicz
2016-11-30 13:28 ` Michal Hocko
2016-11-30 19:58 ` Robin H. Johnson
2016-11-30 20:19 ` drm/radeon spamming alloc_contig_range: [xxx, yyy) PFNs busy busy Robin H. Johnson
2016-11-30 21:24 ` Vlastimil Babka
2016-12-01 6:21 ` Robin H. Johnson
2016-12-01 7:38 ` Vlastimil Babka
2016-12-01 7:58 ` Robin H. Johnson
2016-12-01 7:15 ` Michal Hocko
2016-12-01 7:21 ` Michal Hocko
2016-12-01 7:43 ` Vlastimil Babka
2016-12-01 14:11 ` Michal Hocko
2016-12-01 16:03 ` Michal Nazarewicz [this message]
2016-12-01 16:11 ` Michal Hocko
2016-12-01 21:02 ` Michal Nazarewicz
2016-12-02 6:36 ` Vlastimil Babka
2016-12-02 10:26 ` Lucas Stach
2016-12-02 15:17 ` Jerome Glisse
2016-12-01 1:39 ` PROBLEM-PERSISTS: dmesg spam: alloc_contig_range: [XX, YY) PFNs busy Michal Nazarewicz
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=xa1t37i7ocuv.fsf@mina86.com \
--to=mina86@mina86.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mhocko@kernel.org \
--cc=robbat2@gentoo.org \
--cc=vbabka@suse.cz \
/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