From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Kuehling, Felix" <Felix.Kuehling@amd.com>,
"Yang, Philip" <Philip.Yang@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH] drm: increase drm mmap_range size to 1TB
Date: Thu, 18 Apr 2019 08:32:38 +0100 [thread overview]
Message-ID: <155557275854.4314.17223080641448067981@skylake-alporthouse-com> (raw)
In-Reply-To: <ce68d6f5-317b-ae11-187c-4468dd6f2bc3@suse.de>
Quoting Thomas Zimmermann (2019-04-18 08:29:39)
> Hi
>
> Am 18.04.19 um 00:16 schrieb Kuehling, Felix:
> > Adding dri-devel
> >
> > On 2019-04-17 6:15 p.m., Yang, Philip wrote:
> >> After patch "drm: Use the same mmap-range offset and size for GEM and
> >> TTM", application failed to create bo of system memory because drm
> >> mmap_range size decrease to 64GB from original 1TB. This is not big
> >> enough for applications. Increase the drm mmap_range size to 1TB.
>
> That change in size was accidental. Thanks for restoring the original
> value. The fix will affect GEM as well. If that is not a problem then
>
Why even have an artificial restriction?
-Chris
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-04-18 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 22:15 [PATCH] drm: increase drm mmap_range size to 1TB Yang, Philip
[not found] ` <20190417221507.933-1-Philip.Yang-5C7GfCeVMHo@public.gmane.org>
2019-04-17 22:16 ` Kuehling, Felix
[not found] ` <c8d289ef-75dc-163e-bea5-cd0d429d8614-5C7GfCeVMHo@public.gmane.org>
2019-04-18 7:29 ` Thomas Zimmermann
2019-04-18 7:32 ` Chris Wilson [this message]
2019-04-18 8:30 ` Christian König
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=155557275854.4314.17223080641448067981@skylake-alporthouse-com \
--to=chris@chris-wilson.co.uk \
--cc=Felix.Kuehling@amd.com \
--cc=Philip.Yang@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
/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.