All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bestel <xavier.bestel@free.fr>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andrea Arcangeli <andrea@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: kswapd and MM overload fix
Date: 06 Jun 2001 09:54:04 +0200	[thread overview]
Message-ID: <991814046.30689.0.camel@nomade> (raw)
In-Reply-To: <Pine.LNX.4.31.0106051650340.10118-100000@penguin.transmeta.com>
In-Reply-To: <Pine.LNX.4.31.0106051650340.10118-100000@penguin.transmeta.com>

On 05 Jun 2001 16:51:13 -0700, Linus Torvalds wrote:
> 
> 
> On Wed, 6 Jun 2001, Andrea Arcangeli wrote:
> >
> > that would fix it too indeed, OTOH I think changing the empty zone
> > handling in the kernel is beyond the scope of the bugfix (grep for
> > zone->size in mm/*.c :). Certainly making empty zones transparent to the
> > vm sounds much cleaner from a mm/*.c point of view but it may be faster
> > to skip the block with a branch instead of always computing it.
> 
> Agreed. I'd like to do both. Having uninitialized random stuff around and
> depending on jumping over code that might access it sounds like really bad
> practice.

Why not explicitely initializing it to weird values, to catch code which
should jump over it (but doesn't) ?

Xav


  reply	other threads:[~2001-06-06  7:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-05 22:44 kswapd and MM overload fix Andrea Arcangeli
2001-06-05 23:16 ` Linus Torvalds
2001-06-05 23:48   ` Andrea Arcangeli
2001-06-05 23:51     ` Linus Torvalds
2001-06-06  7:54       ` Xavier Bestel [this message]
2001-06-05 23:48   ` Roger Larsson

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=991814046.30689.0.camel@nomade \
    --to=xavier.bestel@free.fr \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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.