On 03/04/2014 07:21 PM, Michal Hocko wrote:
> On Tue 04-03-14 18:56:06, Vladimir Davydov wrote:
>> Hi Johannes, Michal
>>
>> Could you please take a look at this set when you have time?
> I plan to catch up with others as well. I was on vacation last week and
> now catching up with other stuff. I
On Tue 04-03-14 18:56:06, Vladimir Davydov wrote:
> Hi Johannes, Michal
>
> Could you please take a look at this set when you have time?
I plan to catch up with others as well. I was on vacation last week and
now catching up with other stuff. I do understand that this review
"speed" might be
Hi Johannes, Michal
Could you please take a look at this set when you have time?
Thank you.
On 02/26/2014 07:05 PM, Vladimir Davydov wrote:
> Hi,
>
> During my recent attempt to push kmemcg shrinkers, I was pointed out
> that current kmemcg implementation has a serious design flaw - it lacks
>
Hi Johannes, Michal
Could you please take a look at this set when you have time?
Thank you.
On 02/26/2014 07:05 PM, Vladimir Davydov wrote:
Hi,
During my recent attempt to push kmemcg shrinkers, I was pointed out
that current kmemcg implementation has a serious design flaw - it lacks
On Tue 04-03-14 18:56:06, Vladimir Davydov wrote:
Hi Johannes, Michal
Could you please take a look at this set when you have time?
I plan to catch up with others as well. I was on vacation last week and
now catching up with other stuff. I do understand that this review
speed might be really
On 03/04/2014 07:21 PM, Michal Hocko wrote:
On Tue 04-03-14 18:56:06, Vladimir Davydov wrote:
Hi Johannes, Michal
Could you please take a look at this set when you have time?
I plan to catch up with others as well. I was on vacation last week and
now catching up with other stuff. I do
Hi,
During my recent attempt to push kmemcg shrinkers, I was pointed out
that current kmemcg implementation has a serious design flaw - it lacks
reparenting. Currently each memcg cache holds a css ref to its memcg and
does not let it go until the cache is emptied. Although this approach is
Hi,
During my recent attempt to push kmemcg shrinkers, I was pointed out
that current kmemcg implementation has a serious design flaw - it lacks
reparenting. Currently each memcg cache holds a css ref to its memcg and
does not let it go until the cache is emptied. Although this approach is
8 matches
Mail list logo
