On Tue 24-06-14 10:25:32, Xishi Qiu wrote:
> On 2014/6/23 19:29, Michal Hocko wrote:
[...]
> > This doesn't make much sense to me. So you have a problem with latency
> > caused by direct reclaim so you add a new way of direct page cache
> > reclaim.
> >
> >> A user process produces page cache
On Tue 24-06-14 10:25:32, Xishi Qiu wrote:
On 2014/6/23 19:29, Michal Hocko wrote:
[...]
This doesn't make much sense to me. So you have a problem with latency
caused by direct reclaim so you add a new way of direct page cache
reclaim.
A user process produces page cache frequently, so
On 2014/6/23 19:29, Michal Hocko wrote:
> On Mon 23-06-14 10:05:48, Xishi Qiu wrote:
>> On 2014/6/20 23:32, Michal Hocko wrote:
>>
>>> On Fri 20-06-14 15:56:56, Xishi Qiu wrote:
On 2014/6/17 9:35, Xishi Qiu wrote:
> On 2014/6/16 20:50, Rafael Aquini wrote:
>
>> On Mon, Jun
On Mon 23-06-14 10:05:48, Xishi Qiu wrote:
> On 2014/6/20 23:32, Michal Hocko wrote:
>
> > On Fri 20-06-14 15:56:56, Xishi Qiu wrote:
> >> On 2014/6/17 9:35, Xishi Qiu wrote:
> >>
> >>> On 2014/6/16 20:50, Rafael Aquini wrote:
> >>>
> On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko
On 2014/6/23 19:29, Michal Hocko wrote:
On Mon 23-06-14 10:05:48, Xishi Qiu wrote:
On 2014/6/20 23:32, Michal Hocko wrote:
On Fri 20-06-14 15:56:56, Xishi Qiu wrote:
On 2014/6/17 9:35, Xishi Qiu wrote:
On 2014/6/16 20:50, Rafael Aquini wrote:
On Mon, Jun 16, 2014 at 01:14:22PM +0200,
On Mon 23-06-14 10:05:48, Xishi Qiu wrote:
On 2014/6/20 23:32, Michal Hocko wrote:
On Fri 20-06-14 15:56:56, Xishi Qiu wrote:
On 2014/6/17 9:35, Xishi Qiu wrote:
On 2014/6/16 20:50, Rafael Aquini wrote:
On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
On Mon 16-06-14
On 2014/6/20 23:32, Michal Hocko wrote:
> On Fri 20-06-14 15:56:56, Xishi Qiu wrote:
>> On 2014/6/17 9:35, Xishi Qiu wrote:
>>
>>> On 2014/6/16 20:50, Rafael Aquini wrote:
>>>
On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
> On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
On 2014/6/20 23:32, Michal Hocko wrote:
On Fri 20-06-14 15:56:56, Xishi Qiu wrote:
On 2014/6/17 9:35, Xishi Qiu wrote:
On 2014/6/16 20:50, Rafael Aquini wrote:
On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
When system(e.g. smart
On Fri 20-06-14 15:56:56, Xishi Qiu wrote:
> On 2014/6/17 9:35, Xishi Qiu wrote:
>
> > On 2014/6/16 20:50, Rafael Aquini wrote:
> >
> >> On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
> >>> On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
> When system(e.g. smart phone) running for
On 2014/6/17 9:35, Xishi Qiu wrote:
> On 2014/6/16 20:50, Rafael Aquini wrote:
>
>> On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
>>> On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
When system(e.g. smart phone) running for a long time, the cache often
takes
a large
On 2014/6/17 9:35, Xishi Qiu wrote:
On 2014/6/16 20:50, Rafael Aquini wrote:
On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
When system(e.g. smart phone) running for a long time, the cache often
takes
a large memory, maybe the
On Fri 20-06-14 15:56:56, Xishi Qiu wrote:
On 2014/6/17 9:35, Xishi Qiu wrote:
On 2014/6/16 20:50, Rafael Aquini wrote:
On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
When system(e.g. smart phone) running for a long time, the
On 2014/6/16 20:50, Rafael Aquini wrote:
> On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
>> On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
>>> When system(e.g. smart phone) running for a long time, the cache often takes
>>> a large memory, maybe the free memory is less than 50M, then
On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
> On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
> > When system(e.g. smart phone) running for a long time, the cache often takes
> > a large memory, maybe the free memory is less than 50M, then OOM will happen
> > if APP allocate a large
On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
> When system(e.g. smart phone) running for a long time, the cache often takes
> a large memory, maybe the free memory is less than 50M, then OOM will happen
> if APP allocate a large order pages suddenly and memory reclaim too slowly.
Have you ever
On 2014/6/16 18:04, Zhang Yanfei wrote:
> Hi,
>
> On 06/16/2014 05:24 PM, Xishi Qiu wrote:
>> When system(e.g. smart phone) running for a long time, the cache often takes
>> a large memory, maybe the free memory is less than 50M, then OOM will happen
>> if APP allocate a large order pages
Hi,
On 06/16/2014 05:24 PM, Xishi Qiu wrote:
> When system(e.g. smart phone) running for a long time, the cache often takes
> a large memory, maybe the free memory is less than 50M, then OOM will happen
> if APP allocate a large order pages suddenly and memory reclaim too slowly.
If there is
When system(e.g. smart phone) running for a long time, the cache often takes
a large memory, maybe the free memory is less than 50M, then OOM will happen
if APP allocate a large order pages suddenly and memory reclaim too slowly.
Use "echo 3 > /proc/sys/vm/drop_caches" will drop the whole cache,
When system(e.g. smart phone) running for a long time, the cache often takes
a large memory, maybe the free memory is less than 50M, then OOM will happen
if APP allocate a large order pages suddenly and memory reclaim too slowly.
Use echo 3 /proc/sys/vm/drop_caches will drop the whole cache,
Hi,
On 06/16/2014 05:24 PM, Xishi Qiu wrote:
When system(e.g. smart phone) running for a long time, the cache often takes
a large memory, maybe the free memory is less than 50M, then OOM will happen
if APP allocate a large order pages suddenly and memory reclaim too slowly.
If there is
On 2014/6/16 18:04, Zhang Yanfei wrote:
Hi,
On 06/16/2014 05:24 PM, Xishi Qiu wrote:
When system(e.g. smart phone) running for a long time, the cache often takes
a large memory, maybe the free memory is less than 50M, then OOM will happen
if APP allocate a large order pages suddenly and
On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
When system(e.g. smart phone) running for a long time, the cache often takes
a large memory, maybe the free memory is less than 50M, then OOM will happen
if APP allocate a large order pages suddenly and memory reclaim too slowly.
Have you ever seen
On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
When system(e.g. smart phone) running for a long time, the cache often takes
a large memory, maybe the free memory is less than 50M, then OOM will happen
if APP allocate a large order
On 2014/6/16 20:50, Rafael Aquini wrote:
On Mon, Jun 16, 2014 at 01:14:22PM +0200, Michal Hocko wrote:
On Mon 16-06-14 17:24:38, Xishi Qiu wrote:
When system(e.g. smart phone) running for a long time, the cache often takes
a large memory, maybe the free memory is less than 50M, then OOM will
24 matches
Mail list logo
