public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Craig Kulesa <ckulesa@as.arizona.edu>, linux-kernel@vger.kernel.org
Subject: Re: VM in 2.4.10(+tweaks) vs. 2.4.9-ac14/15(+stuff)
Date: Wed, 26 Sep 2001 16:49:35 +0200	[thread overview]
Message-ID: <20010926164935.J27945@athlon.random> (raw)
In-Reply-To: <20010926160347.F27945@athlon.random> <Pine.LNX.4.33L.0109261123070.19147-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0109261123070.19147-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Wed, Sep 26, 2001 at 11:23:44AM -0300

On Wed, Sep 26, 2001 at 11:23:44AM -0300, Rik van Riel wrote:
> On Wed, 26 Sep 2001, Andrea Arcangeli wrote:
> > On Wed, Sep 26, 2001 at 06:38:48AM -0700, Craig Kulesa wrote:
> > > in memory, and is swapping out harder to compensate.  The ac14/ac15 tree
> >
> > 2.4.10 is swapping out more also because I don't keep track of which
> > pages are just uptodate on the swap space. This will be fixed as soon
> > as I teach get_swap_page to collect away from the swapcache mapped
> > exclusive swap pages.
> 
> Wouldn't that be easier to do from try_to_swap_out() ?

Of course that's a possibility but then we'd have to duplicate it in all
other get_swap_page callers, see?

And I think it much better fits hided in get_swap_page: the semantics of
get_swap_page() are "give to the caller a newly allocated swap entry".
So IMHO it is its own business to discard our "optimizations" to
generate a free swap entry in case all swap was just allocated.

Andrea

  reply	other threads:[~2001-09-26 14:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26 13:38 VM in 2.4.10(+tweaks) vs. 2.4.9-ac14/15(+stuff) Craig Kulesa
2001-09-26 14:03 ` Andrea Arcangeli
2001-09-26 14:23   ` Rik van Riel
2001-09-26 14:49     ` Andrea Arcangeli [this message]
2001-09-26 18:17       ` Robert Macaulay
2001-09-26 18:36         ` Andrea Arcangeli
2001-09-27 22:13           ` highmem deadlock fix [was Re: VM in 2.4.10(+tweaks) vs. 2.4.9-ac14/15(+stuff)] Andrea Arcangeli
2001-09-27 22:55             ` J . A . Magallon
2001-09-27 23:16             ` Linus Torvalds
2001-09-27 23:18               ` Linus Torvalds
2001-09-27 23:37                 ` Andrea Arcangeli
2001-09-27 23:51                   ` Rik van Riel
2001-09-28  1:26                     ` Andrea Arcangeli
2001-09-28  1:28                     ` Linus Torvalds
2001-09-27 23:47               ` Andrea Arcangeli
2001-09-28  0:03                 ` Linus Torvalds
2001-09-28  0:11                   ` Andrea Arcangeli
2001-09-28  2:12                 ` Robert Macaulay
2001-09-28  2:24                   ` Andrea Arcangeli
2001-09-28 13:36                     ` Robert Macaulay
2001-09-28 14:02                     ` LILO causes segmentation fault and panic [was Re: highmem deadlock fix] Robert Macaulay
2001-09-28  0:08               ` highmem deadlock fix [was Re: VM in 2.4.10(+tweaks) vs. 2.4.9-ac14/15(+stuff)] Andrea Arcangeli
     [not found] <Pine.LNX.4.33.0109261706010.25812-201000@ping.us.dell.com>
2001-09-26 22:54 ` VM in 2.4.10(+tweaks) vs. 2.4.9-ac14/15(+stuff) Robert Macaulay
2001-09-27  2:30   ` Keith Owens

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=20010926164935.J27945@athlon.random \
    --to=andrea@suse.de \
    --cc=ckulesa@as.arizona.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox