dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Hellstrom <thellstrom@vmware.com>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: ttm: merge ttm_backend & ttm_tt, introduce ttm dma allocator V5
Date: Mon, 14 Nov 2011 20:25:54 +0100	[thread overview]
Message-ID: <4EC16B42.3070000@vmware.com> (raw)
In-Reply-To: <20111114185427.GA5300@homer.localdomain>

On 11/14/2011 07:54 PM, Jerome Glisse wrote:
> On Mon, Nov 14, 2011 at 05:06:42PM +0100, Thomas Hellstrom wrote:
>    
>> On 11/14/2011 05:02 PM, Jerome Glisse wrote:
>>      
>>> On Mon, Nov 14, 2011 at 9:49 AM, Thomas Hellstrom<thellstrom@vmware.com>   wrote:
>>>        
>>>> On 11/11/2011 11:47 PM, j.glisse@gmail.com wrote:
>>>>          
>>>>> So attached is updated serie of patch with fixes for swaping issue
>>>>> that also impacted memory accounting.
>>>>>            
>>>> Jerome,
>>>> Out of interest, what was the swapping issue?
>>>>
>>>> /Thomas
>>>>
>>>>
>>>>          
>>> The page list was NULL and some access ended up freaking the kernel
>>> and oom kicked in for some reason i still don't understand. Bottom
>>> line things were going south in a split second leaving me with no log
>>> or access, i thought it was accounting not working as it was what i
>>> tested at the time. I should have tested accouting without the
>>> patchset
>>>
>>> Cheers,
>>> Jerome
>>>        
>> Still, I think you have a point in the fact that *when* finally the
>> OOM killer kicks in,
>> it probably doesn't have a way to associate user-space created bos
>> with processes
>> and kill the right process.
>>
>> /Thomas
>>
>>      
> Btw can you review patch 14 as it touch vmwgfx, i am pretty sure
> i got it right.
>
> Cheers,
> Jerome
>    
Yes I will do a more thorough review tomorrow of all unreviewed stuff.

/Thomas

  reply	other threads:[~2011-11-14 19:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 22:47 ttm: merge ttm_backend & ttm_tt, introduce ttm dma allocator V5 j.glisse
2011-11-11 22:47 ` [PATCH 01/14] swiotlb: Expose swiotlb_nr_tlb function to modules j.glisse
2011-11-11 22:47 ` [PATCH 02/14] drm/ttm: remove userspace backed ttm object support j.glisse
2011-11-11 22:47 ` [PATCH 03/14] drm/ttm: remove split btw highmen and lowmem page j.glisse
2011-11-11 22:47 ` [PATCH 04/14] drm/ttm: remove unused backend flags field j.glisse
2011-11-11 22:47 ` [PATCH 05/14] drm/ttm: use ttm put pages function to properly restore cache attribute j.glisse
2011-11-11 22:47 ` [PATCH 06/14] drm/ttm: test for dma_address array allocation failure j.glisse
2011-11-11 22:47 ` [PATCH 07/14] drm/ttm: page allocation use page array instead of list j.glisse
2011-11-11 22:47 ` [PATCH 08/14] drm/ttm: merge ttm_backend and ttm_tt V5 j.glisse
2011-11-11 22:47 ` [PATCH 09/14] drm/ttm: introduce callback for ttm_tt populate & unpopulate V4 j.glisse
2011-11-11 22:47 ` [PATCH 10/14] drm/ttm: provide dma aware ttm page pool code V8 j.glisse
2011-11-16 15:50   ` Konrad Rzeszutek Wilk
2011-11-16 16:04     ` Jerome Glisse
2011-11-11 22:47 ` [PATCH 11/14] drm/radeon/kms: enable the ttm dma pool if swiotlb is on V3 j.glisse
2011-11-16 15:46   ` Konrad Rzeszutek Wilk
2011-11-16 16:05     ` Jerome Glisse
2011-11-11 22:47 ` [PATCH 12/14] drm/nouveau: enable the ttm dma pool when swiotlb is active V3 j.glisse
2011-11-11 22:47 ` [PATCH 13/14] drm/ttm: isolate dma data from ttm_tt V3 j.glisse
2011-11-15 21:07   ` Konrad Rzeszutek Wilk
2011-11-15 21:47     ` Jerome Glisse
2011-11-16  0:35     ` Jerome Glisse
2011-11-16 17:21       ` Konrad Rzeszutek Wilk
2011-11-11 22:47 ` [PATCH 14/14] drm/ttm: simplify memory accounting for ttm user j.glisse
2011-11-14 14:49 ` ttm: merge ttm_backend & ttm_tt, introduce ttm dma allocator V5 Thomas Hellstrom
2011-11-14 16:02   ` Jerome Glisse
2011-11-14 16:06     ` Thomas Hellstrom
2011-11-14 18:54       ` Jerome Glisse
2011-11-14 19:25         ` Thomas Hellstrom [this message]
2011-11-16 15:15         ` Konrad Rzeszutek Wilk
2011-11-16 15:31           ` Jerome Glisse
2011-11-16 15:53             ` Konrad Rzeszutek Wilk

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=4EC16B42.3070000@vmware.com \
    --to=thellstrom@vmware.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=j.glisse@gmail.com \
    /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