On Fri, Dec 19, 2014 at 09:46:48AM +0900, Minchan Kim wrote:
> Hey Seth,
>
> On Wed, Dec 17, 2014 at 05:19:30PM -0600, Seth Jennings wrote:
> > On Tue, Dec 02, 2014 at 11:49:41AM +0900, Minchan Kim wrote:
> > > Recently, there was issue about zsmalloc fragmentation and
> > > I got a report from
On Fri, Dec 19, 2014 at 09:46:48AM +0900, Minchan Kim wrote:
Hey Seth,
On Wed, Dec 17, 2014 at 05:19:30PM -0600, Seth Jennings wrote:
On Tue, Dec 02, 2014 at 11:49:41AM +0900, Minchan Kim wrote:
Recently, there was issue about zsmalloc fragmentation and
I got a report from Juno that
Hey Seth,
On Wed, Dec 17, 2014 at 05:19:30PM -0600, Seth Jennings wrote:
> On Tue, Dec 02, 2014 at 11:49:41AM +0900, Minchan Kim wrote:
> > Recently, there was issue about zsmalloc fragmentation and
> > I got a report from Juno that new fork failed although there
> > are plenty of free pages in
Hey Seth,
On Wed, Dec 17, 2014 at 05:19:30PM -0600, Seth Jennings wrote:
On Tue, Dec 02, 2014 at 11:49:41AM +0900, Minchan Kim wrote:
Recently, there was issue about zsmalloc fragmentation and
I got a report from Juno that new fork failed although there
are plenty of free pages in the
2014-12-18 7:19 GMT+08:00 Seth Jennings :
> On Tue, Dec 02, 2014 at 11:49:41AM +0900, Minchan Kim wrote:
>> Recently, there was issue about zsmalloc fragmentation and
>> I got a report from Juno that new fork failed although there
>> are plenty of free pages in the system.
>> His investigation
On Tue, Dec 02, 2014 at 11:49:41AM +0900, Minchan Kim wrote:
> Recently, there was issue about zsmalloc fragmentation and
> I got a report from Juno that new fork failed although there
> are plenty of free pages in the system.
> His investigation revealed zram is one of the culprit to make
> heavy
On Tue, Dec 02, 2014 at 11:49:41AM +0900, Minchan Kim wrote:
Recently, there was issue about zsmalloc fragmentation and
I got a report from Juno that new fork failed although there
are plenty of free pages in the system.
His investigation revealed zram is one of the culprit to make
heavy
2014-12-18 7:19 GMT+08:00 Seth Jennings sjenni...@variantweb.net:
On Tue, Dec 02, 2014 at 11:49:41AM +0900, Minchan Kim wrote:
Recently, there was issue about zsmalloc fragmentation and
I got a report from Juno that new fork failed although there
are plenty of free pages in the system.
His
Hi, Minchan.
I got it. Thank u :).
Seungho.
2014-12-04 오후 4:20에 Minchan Kim 이(가) 쓴 글:
Hey Seungho,
On Thu, Dec 04, 2014 at 03:49:21PM +0900, "박승호/책임연구원/SW
Platform(연)AOT팀(seungho1.p...@lge.com)" wrote:
Hi, Minchan.
I have a question.
The problem mentioned can't be resolved with
Hi, Minchan.
Sorry, I got it. You made zsmalloc pages movable.
forget it.
Seungho.
2014-12-04 오후 3:49에 "박승호/책임연구원/SW Platform(연)AOT팀
(seungho1.p...@lge.com)" 이(가) 쓴 글:
Hi, Minchan.
I have a question.
The problem mentioned can't be resolved with compaction?
Is there any reason that zsmalloc
Hey Seungho,
On Thu, Dec 04, 2014 at 03:49:21PM +0900, "박승호/책임연구원/SW
Platform(연)AOT팀(seungho1.p...@lge.com)" wrote:
> Hi, Minchan.
>
> I have a question.
> The problem mentioned can't be resolved with compaction?
> Is there any reason that zsmalloc pages can't be moved by compaction
> operation
Hi, Minchan.
I have a question.
The problem mentioned can't be resolved with compaction?
Is there any reason that zsmalloc pages can't be moved by compaction
operation in direct reclaim?
2014-12-02 오전 11:49에 Minchan Kim 이(가) 쓴 글:
Recently, there was issue about zsmalloc fragmentation and
I got
Hi, Minchan.
I have a question.
The problem mentioned can't be resolved with compaction?
Is there any reason that zsmalloc pages can't be moved by compaction
operation in direct reclaim?
2014-12-02 오전 11:49에 Minchan Kim 이(가) 쓴 글:
Recently, there was issue about zsmalloc fragmentation and
I got
Hey Seungho,
On Thu, Dec 04, 2014 at 03:49:21PM +0900, 박승호/책임연구원/SW
Platform(연)AOT팀(seungho1.p...@lge.com) wrote:
Hi, Minchan.
I have a question.
The problem mentioned can't be resolved with compaction?
Is there any reason that zsmalloc pages can't be moved by compaction
operation in
Hi, Minchan.
Sorry, I got it. You made zsmalloc pages movable.
forget it.
Seungho.
2014-12-04 오후 3:49에 박승호/책임연구원/SW Platform(연)AOT팀
(seungho1.p...@lge.com) 이(가) 쓴 글:
Hi, Minchan.
I have a question.
The problem mentioned can't be resolved with compaction?
Is there any reason that zsmalloc
Hi, Minchan.
I got it. Thank u :).
Seungho.
2014-12-04 오후 4:20에 Minchan Kim 이(가) 쓴 글:
Hey Seungho,
On Thu, Dec 04, 2014 at 03:49:21PM +0900, 박승호/책임연구원/SW
Platform(연)AOT팀(seungho1.p...@lge.com) wrote:
Hi, Minchan.
I have a question.
The problem mentioned can't be resolved with compaction?
Recently, there was issue about zsmalloc fragmentation and
I got a report from Juno that new fork failed although there
are plenty of free pages in the system.
His investigation revealed zram is one of the culprit to make
heavy fragmentation so there was no more contiguous 16K page
for pgd to fork
Recently, there was issue about zsmalloc fragmentation and
I got a report from Juno that new fork failed although there
are plenty of free pages in the system.
His investigation revealed zram is one of the culprit to make
heavy fragmentation so there was no more contiguous 16K page
for pgd to fork
18 matches
Mail list logo
