On Thu, May 29, 2014 at 02:23:08PM -0700, Eric Dumazet wrote:
> On Thu, 2014-05-29 at 13:05 -0700, Andrew Morton wrote:
> > On Thu, 29 May 2014 15:22:34 +0900 Joonsoo Kim
> > wrote:
> >
> > > Richard Yao reported a month ago that his system have a trouble
> > > with vmap_area_lock contention
On Thu, 2014-05-29 at 13:05 -0700, Andrew Morton wrote:
> On Thu, 29 May 2014 15:22:34 +0900 Joonsoo Kim wrote:
>
> > Richard Yao reported a month ago that his system have a trouble
> > with vmap_area_lock contention during performance analysis
> > by /proc/meminfo. Andrew asked why his analysis
On Thu, 29 May 2014 15:22:34 +0900 Joonsoo Kim wrote:
> Richard Yao reported a month ago that his system have a trouble
> with vmap_area_lock contention during performance analysis
> by /proc/meminfo. Andrew asked why his analysis checks /proc/meminfo
> stressfully, but he didn't answer it.
>
>
I do not have a way of tracing it. I meant to reply when I did, but that has
not changed. That being said, I like this patch.
On May 29, 2014, at 2:22 AM, Joonsoo Kim wrote:
> Richard Yao reported a month ago that his system have a trouble
> with vmap_area_lock contention during performance
On Thu, 2014-05-29 at 15:22 +0900, Joonsoo Kim wrote:
> Richard Yao reported a month ago that his system have a trouble
> with vmap_area_lock contention during performance analysis
> by /proc/meminfo. Andrew asked why his analysis checks /proc/meminfo
> stressfully, but he didn't answer it.
>
>
Richard Yao reported a month ago that his system have a trouble
with vmap_area_lock contention during performance analysis
by /proc/meminfo. Andrew asked why his analysis checks /proc/meminfo
stressfully, but he didn't answer it.
https://lkml.org/lkml/2014/4/10/416
Although I'm not sure that
Richard Yao reported a month ago that his system have a trouble
with vmap_area_lock contention during performance analysis
by /proc/meminfo. Andrew asked why his analysis checks /proc/meminfo
stressfully, but he didn't answer it.
https://lkml.org/lkml/2014/4/10/416
Although I'm not sure that
On Thu, 2014-05-29 at 15:22 +0900, Joonsoo Kim wrote:
Richard Yao reported a month ago that his system have a trouble
with vmap_area_lock contention during performance analysis
by /proc/meminfo. Andrew asked why his analysis checks /proc/meminfo
stressfully, but he didn't answer it.
I do not have a way of tracing it. I meant to reply when I did, but that has
not changed. That being said, I like this patch.
On May 29, 2014, at 2:22 AM, Joonsoo Kim iamjoonsoo@lge.com wrote:
Richard Yao reported a month ago that his system have a trouble
with vmap_area_lock contention
On Thu, 29 May 2014 15:22:34 +0900 Joonsoo Kim iamjoonsoo@lge.com wrote:
Richard Yao reported a month ago that his system have a trouble
with vmap_area_lock contention during performance analysis
by /proc/meminfo. Andrew asked why his analysis checks /proc/meminfo
stressfully, but he
On Thu, 2014-05-29 at 13:05 -0700, Andrew Morton wrote:
On Thu, 29 May 2014 15:22:34 +0900 Joonsoo Kim iamjoonsoo@lge.com wrote:
Richard Yao reported a month ago that his system have a trouble
with vmap_area_lock contention during performance analysis
by /proc/meminfo. Andrew asked
On Thu, May 29, 2014 at 02:23:08PM -0700, Eric Dumazet wrote:
On Thu, 2014-05-29 at 13:05 -0700, Andrew Morton wrote:
On Thu, 29 May 2014 15:22:34 +0900 Joonsoo Kim iamjoonsoo@lge.com
wrote:
Richard Yao reported a month ago that his system have a trouble
with vmap_area_lock
12 matches
Mail list logo
