All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: Comment on patch to remove nr_async_pages limit
Date: 05 Jun 2001 17:57:45 +0200	[thread overview]
Message-ID: <873d9ezzpi.fsf@atlas.iskon.hr> (raw)
In-Reply-To: <Pine.LNX.4.33.0106050820540.867-100000@mikeg.weiden.de>
In-Reply-To: <Pine.LNX.4.33.0106050820540.867-100000@mikeg.weiden.de> (Mike Galbraith's message of "Tue, 5 Jun 2001 09:38:08 +0200 (CEST)")

Mike Galbraith <mikeg@wen-online.de> writes:

> On Mon, 4 Jun 2001, Marcelo Tosatti wrote:
> 
> > Zlatko,
> >
> > I've read your patch to remove nr_async_pages limit while reading an
> > archive on the web. (I have to figure out why lkml is not being delivered
> > correctly to me...)
> >
> > Quoting your message:
> >
> > "That artificial limit hurts both swap out and swap in path as it
> > introduces synchronization points (and/or weakens swapin readahead),
> > which I think are not necessary."
> >
> > If we are under low memory, we cannot simply writeout a whole bunch of
> > swap data. Remember the writeout operations will potentially allocate
> > buffer_head's for the swapcache pages before doing real IO, which takes
> > _more memory_: OOM deadlock.
> 
> What's the point of creating swapcache pages, and then avoiding doing
> the IO until it becomes _dangerous_ to do so?  That's what we're doing
> right now.  This is a problem because we guarantee it will become one.
> We guarantee that the pagecache will become almost pure swapcache by
> delaying the writeout so long that everything else is consumed.
> 

Huh, this looks just like my argument, just put in different words. I
should have read this sooner. :)
-- 
Zlatko

WARNING: multiple messages have this Message-ID (diff)
From: Zlatko Calusic <zlatko.calusic@iskon.hr>
To: Mike Galbraith <mikeg@wen-online.de>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: Comment on patch to remove nr_async_pages limit
Date: 05 Jun 2001 17:57:45 +0200	[thread overview]
Message-ID: <873d9ezzpi.fsf@atlas.iskon.hr> (raw)
In-Reply-To: <Pine.LNX.4.33.0106050820540.867-100000@mikeg.weiden.de> (Mike Galbraith's message of "Tue, 5 Jun 2001 09:38:08 +0200 (CEST)")

Mike Galbraith <mikeg@wen-online.de> writes:

> On Mon, 4 Jun 2001, Marcelo Tosatti wrote:
> 
> > Zlatko,
> >
> > I've read your patch to remove nr_async_pages limit while reading an
> > archive on the web. (I have to figure out why lkml is not being delivered
> > correctly to me...)
> >
> > Quoting your message:
> >
> > "That artificial limit hurts both swap out and swap in path as it
> > introduces synchronization points (and/or weakens swapin readahead),
> > which I think are not necessary."
> >
> > If we are under low memory, we cannot simply writeout a whole bunch of
> > swap data. Remember the writeout operations will potentially allocate
> > buffer_head's for the swapcache pages before doing real IO, which takes
> > _more memory_: OOM deadlock.
> 
> What's the point of creating swapcache pages, and then avoiding doing
> the IO until it becomes _dangerous_ to do so?  That's what we're doing
> right now.  This is a problem because we guarantee it will become one.
> We guarantee that the pagecache will become almost pure swapcache by
> delaying the writeout so long that everything else is consumed.
> 

Huh, this looks just like my argument, just put in different words. I
should have read this sooner. :)
-- 
Zlatko
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  parent reply	other threads:[~2001-06-05 16:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-05  1:04 Comment on patch to remove nr_async_pages limit Marcelo Tosatti
2001-06-05  1:04 ` Marcelo Tosatti
2001-06-05  7:38 ` Mike Galbraith
2001-06-05  7:38   ` Mike Galbraith
2001-06-05  6:18   ` Marcelo Tosatti
2001-06-05  6:18     ` Marcelo Tosatti
2001-06-05 10:32     ` Mike Galbraith
2001-06-05 10:32       ` Mike Galbraith
2001-06-05 11:42       ` Ed Tomlinson
2001-06-05 11:42         ` Ed Tomlinson
2001-06-05 16:08         ` Zlatko Calusic
2001-06-05 16:08           ` Zlatko Calusic
2001-06-05 19:21       ` Benjamin C.R. LaHaise
2001-06-05 19:21         ` Benjamin C.R. LaHaise
2001-06-05 21:00         ` Comment on patch to remove nr_async_pages limitA Mike Galbraith
2001-06-05 21:00           ` Mike Galbraith
2001-06-05 22:21           ` Daniel Phillips
2001-06-05 22:21             ` Daniel Phillips
2001-06-05 16:05     ` Comment on patch to remove nr_async_pages limit Zlatko Calusic
2001-06-05 16:05       ` Zlatko Calusic
2001-06-09  3:09       ` Rik van Riel
2001-06-09  3:09         ` Rik van Riel
2001-06-09  6:07         ` Mike Galbraith
2001-06-09  6:07           ` Mike Galbraith
2001-06-05 15:57   ` Zlatko Calusic [this message]
2001-06-05 15:57     ` Zlatko Calusic
2001-06-05 15:56 ` Zlatko Calusic
2001-06-05 15:56   ` Zlatko Calusic

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=873d9ezzpi.fsf@atlas.iskon.hr \
    --to=zlatko.calusic@iskon.hr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=marcelo@conectiva.com.br \
    --cc=mikeg@wen-online.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.