From: ebiederm@xmission.com (Eric W. Biederman)
To: Rik van Riel <riel@conectiva.com.br>
Cc: "David S. Miller" <davem@redhat.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: 2.4.14 + Bug in swap_out.
Date: 21 Nov 2001 07:21:45 -0700 [thread overview]
Message-ID: <m1d72c19xi.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111211219420.1491-100000@duckman.distro.conectiva>
In-Reply-To: <Pine.LNX.4.33L.0111211219420.1491-100000@duckman.distro.conectiva>
Rik van Riel <riel@conectiva.com.br> writes:
> On 21 Nov 2001, Eric W. Biederman wrote:
>
> > We only hold a ref count for the duration of swap_out_mm.
> > Not for the duration of the value in swap_mm.
>
> In that case, why can't we just take the next mm from
> init_mm and just "roll over" our mm to the back of the
> list once we're done with it ?
Sounds good to me. Unless we have another user for that list.
> Removing magic is good ;)
Definitely. Things that are locally correct are much easier
to verify and trust. I'm satisfied for the moment that it isn't
actually broken. But more obvious code is definitely a plus
if we can get it.
Eric
WARNING: multiple messages have this Message-ID (diff)
From: ebiederm@xmission.com (Eric W. Biederman)
To: Rik van Riel <riel@conectiva.com.br>
Cc: "David S. Miller" <davem@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: 2.4.14 + Bug in swap_out.
Date: 21 Nov 2001 07:21:45 -0700 [thread overview]
Message-ID: <m1d72c19xi.fsf@frodo.biederman.org> (raw)
In-Reply-To: <Pine.LNX.4.33L.0111211219420.1491-100000@duckman.distro.conectiva>
Rik van Riel <riel@conectiva.com.br> writes:
> On 21 Nov 2001, Eric W. Biederman wrote:
>
> > We only hold a ref count for the duration of swap_out_mm.
> > Not for the duration of the value in swap_mm.
>
> In that case, why can't we just take the next mm from
> init_mm and just "roll over" our mm to the back of the
> list once we're done with it ?
Sounds good to me. Unless we have another user for that list.
> Removing magic is good ;)
Definitely. Things that are locally correct are much easier
to verify and trust. I'm satisfied for the moment that it isn't
actually broken. But more obvious code is definitely a plus
if we can get it.
Eric
--
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/
next prev parent reply other threads:[~2001-11-21 14:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 6:01 2.4.14 + Bug in swap_out Eric W. Biederman
2001-11-21 6:01 ` Eric W. Biederman
2001-11-21 6:29 ` David S. Miller
2001-11-21 6:29 ` David S. Miller
2001-11-21 6:37 ` Eric W. Biederman
2001-11-21 6:37 ` Eric W. Biederman
2001-11-21 12:17 ` Rik van Riel
2001-11-21 12:17 ` Rik van Riel
2001-11-21 13:31 ` Eric W. Biederman
2001-11-21 13:31 ` Eric W. Biederman
2001-11-21 14:20 ` Rik van Riel
2001-11-21 14:20 ` Rik van Riel
2001-11-21 14:21 ` Eric W. Biederman [this message]
2001-11-21 14:21 ` Eric W. Biederman
2001-11-21 15:34 ` Hugh Dickins
2001-11-21 15:39 ` Rik van Riel
2001-11-21 15:39 ` Rik van Riel
2001-11-21 16:19 ` Hugh Dickins
2001-11-21 16:26 ` Eric W. Biederman
2001-11-21 16:26 ` Eric W. Biederman
2001-11-21 17:45 ` Hugh Dickins
2001-11-21 12:13 ` Rik van Riel
2001-11-21 12:13 ` Rik van Riel
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=m1d72c19xi.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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.