linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Kanoj Sarcar <kanoj@google.engr.sgi.com>,
	sct@redhat.com, Gerhard.Wichert@pdb.siemens.de,
	Winfried.Gerhard@pdb.siemens.de, linux-kernel@vger.rutgers.edu,
	linux-mm@kvack.org
Subject: Re: [bigmem-patch] 4GB with Linux on IA32
Date: Mon, 16 Aug 1999 23:29:48 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.9908162324001.1048-100000@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9908162358590.9951-100000@laser.random>


On Tue, 17 Aug 1999, Andrea Arcangeli wrote:
>
> This incremental (against bigmem-2.3.13-L) patch will fix the ptrace and
> /proc/*/mem read/writes to other process VM inside the kernel.

Andrea, you really need to clean these things up.

The bigmem patches look fine _except_ for the fact that they have these 

	#ifdef CONFIG_BIGMEM

turds all over the place. That's NOT how to do it.

Instead, you should unconditionally always do

	#include <linux/bigmem.h>

which in turn does something like this:

	#ifdef CONFIG_BIGMEM

	  #include <asm/bigmem.h>

	#else

	  #define kmap(page)	page_address(page)
	  #define kunmap(page)	do { } while (0)

	#endif

and then there is not a _single_ #ifdef inside any actual code.

Remember: if you have to have #ifdef's in actual functional code, you're
doing something wrong. I don't see why you can't just abstract the thing
away with zero performance degradation for the non-bigmem case by just
making the mapping function the existing identity function.

I'd like you to do the above cleanup, and then the bigmem patches look
like they could easily be integrated into the current 2.3.x series. But
with #ifdef's it won't.

			Linus

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

  parent reply	other threads:[~1999-08-17  6:29 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-16 16:29 Andrea Arcangeli
1999-08-16 16:48 ` Matthew Wilcox
1999-08-16 17:19   ` Andrea Arcangeli
1999-08-16 18:43 ` Kanoj Sarcar
1999-08-16 19:43   ` Alan Cox
1999-08-16 20:54     ` Andrea Arcangeli
1999-08-16 22:47       ` Andrea Arcangeli
1999-08-16 23:26         ` Andrea Arcangeli
1999-08-16 23:39           ` Kanoj Sarcar
1999-08-17  0:10             ` Andrea Arcangeli
1999-08-17  6:37               ` Kanoj Sarcar
1999-08-17  6:41                 ` Linus Torvalds
1999-08-17  6:50                   ` Kanoj Sarcar
1999-08-17  7:03                     ` Linus Torvalds
1999-08-17  7:23                       ` Linus Torvalds
1999-08-17 11:39                         ` Alan Cox
1999-08-26 16:27                           ` Andrea Arcangeli
1999-08-17 11:46                     ` Alan Cox
1999-08-17 14:26             ` Andrea Arcangeli
1999-08-17  6:39           ` Linus Torvalds
1999-08-17 12:40             ` Andrea Arcangeli
1999-08-17  6:29         ` Linus Torvalds [this message]
1999-08-17 12:37           ` Andrea Arcangeli
1999-08-17 14:04             ` Andrea Arcangeli
1999-08-17  8:52         ` Jakub Jelinek
1999-08-17  9:13         ` Pavel Machek
1999-08-18 14:08           ` Andrea Arcangeli
1999-08-19 12:20             ` Andrea Arcangeli
1999-08-16 23:28       ` Kanoj Sarcar
1999-08-16 23:49         ` Andrea Arcangeli
1999-08-17  6:29         ` David S. Miller
1999-08-17 12:38           ` Andrea Arcangeli
1999-08-17  0:17       ` Andrea Arcangeli
1999-08-19 13:33         ` Thierry Vignaud
1999-08-19 16:49           ` Stephen C. Tweedie
1999-08-20  7:35             ` Thierry Vignaud
1999-08-20  9:55               ` Alan Cox
1999-08-20 18:25               ` Linus Torvalds
1999-08-16 20:34   ` Andrea Arcangeli

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=Pine.LNX.4.10.9908162324001.1048-100000@penguin.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=Gerhard.Wichert@pdb.siemens.de \
    --cc=Winfried.Gerhard@pdb.siemens.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrea@suse.de \
    --cc=kanoj@google.engr.sgi.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=sct@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox