linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: x-linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Cc: "Wichert, Gerhard" <Gerhard.Wichert@pdb.siemens.de>,
	"Gerhard, Winfried" <Winfried.Gerhard@pdb.siemens.de>
Subject: Re: [bigmem-patch] 4GB with Linux on IA32
Date: Thu, 19 Aug 1999 14:20:49 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.10.9908191415550.489-101000@laser.random> (raw)
In-Reply-To: <Pine.LNX.4.10.9908181601390.4343-100000@laser.random>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 668 bytes --]

On Wed, 18 Aug 1999, Andrea Arcangeli wrote:

>Now I am cleaning up the stuff still more putting all the bigmem common
>code and variables in linux/mm/bigmem.c (separated by the arch specific
>arch/i386/mm/bigmem.c) so there won't be duplicated sources if some other
>arch (not only i386) will want to take advantage of the bigmem common
>interface (I just heard some interest in this field ;).

I did the cleanup. The latest bigmem-2.3.14-pre2-O patch is attached to
this email. There aren't real functional differences in the code. It's
only a low-priority architecture-cleanup diff (if you are just using
bigmem-2.3.13-N you can safely ignore this update).

Andrea

[-- Attachment #2: bigmem with arch-cleanup --]
[-- Type: APPLICATION/OCTET-STREAM, Size: 9308 bytes --]

  reply	other threads:[~1999-08-19 12:20 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
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 [this message]
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.9908191415550.489-101000@laser.random \
    --to=andrea@suse.de \
    --cc=Gerhard.Wichert@pdb.siemens.de \
    --cc=Winfried.Gerhard@pdb.siemens.de \
    --cc=linux-mm@kvack.org \
    --cc=x-linux-kernel@vger.rutgers.edu \
    /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