From: "Breton M. Saunders" <brett@mynah-software.com>
To: Dave Airlie <airlied@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: significant ioremap leak in i915?
Date: Sun, 12 Oct 2014 12:07:06 +0100 [thread overview]
Message-ID: <543A60DA.1020200@mynah-software.com> (raw)
In-Reply-To: <CAPM=9tziAwd7pF7YX8ipWRbEJcX+S2AvDp5-gC24_=o+WALMqQ@mail.gmail.com>
On 12/10/14 11:23, Dave Airlie wrote:
> On 12 October 2014 19:28, Breton M. Saunders <brett@mynah-software.com> wrote:
>> Guys,
>>
>> This might be covered elsewhere, but help me come up to speed: I am
>> trying to analyze a leak in i915 that occurs on a digital sinage system that
>> I've built. The system basically is doing a lot of XCompositeRedirectWindow
>> / glXBindTexImageEXT calls to render web views and mplayer output onto
>> opengl textures for subsequent rendering.
>>
>> In my testing, I observe that an enormous block is being lost in ioremap
>> by looking at /proc/vmallocinfo:
>>
>> <snip>
>> 0xffffc90000200000-0xffffc90010201000 268439552 pci_mmcfg_arch_map+0x33/0x90
>> phys=e0000000 ioremap
>> <snip>
>> 0xffffc90010f80000-0xffffc90020f81000 268439552 i915_driver_load+0x20c/0x6d0
>> [i915] phys=c0000000 ioremap
>> <snip>
>>
>> So in this example 268 megabytes have been lost.
>
> This isn't RAM, its address space mapping, its not really a leak at all.
It really doesn't matter whether it is ram or mapping; its a resource
leak that causes the system to OOM and panic.
-Brett
next prev parent reply other threads:[~2014-10-12 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 9:28 significant ioremap leak in i915? Breton M. Saunders
2014-10-12 10:23 ` Dave Airlie
2014-10-12 11:07 ` Breton M. Saunders [this message]
2014-10-13 1:09 ` Dave Airlie
2014-10-13 4:58 ` Breton M. Saunders
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=543A60DA.1020200@mynah-software.com \
--to=brett@mynah-software.com \
--cc=airlied@gmail.com \
--cc=intel-gfx@lists.freedesktop.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 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.