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: Mon, 13 Oct 2014 05:58:02 +0100 [thread overview]
Message-ID: <543B5BDA.2030306@mynah-software.com> (raw)
In-Reply-To: <CAPM=9twwoLUECY0khjPy_y3Mxaeaho3hLF74B94A5oWQEeE6Aw@mail.gmail.com>
On 13/10/14 02:09, Dave Airlie wrote:
>>>> 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.
> hey I was trying to help you come up to speed as requested, you don't
> have to believe me.
I apologize, and I appreciate your help.
I do believe you.
It also appears that the mapping I jumped on wasn't the root cause of
the problem; I'm still investigating.
-Brett
prev parent reply other threads:[~2014-10-13 4:58 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
2014-10-13 1:09 ` Dave Airlie
2014-10-13 4:58 ` Breton M. Saunders [this message]
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=543B5BDA.2030306@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox