From: "Fernando Alencar Maróstica" <famarost@unimep.br>
To: David Weinehall <tao@acc.umu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.0] Fixed kernel stuff
Date: 21 Oct 2002 17:49:04 -0200 [thread overview]
Message-ID: <1035229745.625.0.camel@nitrogenium> (raw)
In-Reply-To: <20021015211103.GV26715@khan.acc.umu.se>
> Since you are doing changes to the VM, I would like detail descriptions
> of what each change does, and why it is necessary, stability- or
> security-wise. I will not accept changes to the VM subsystem unless
> there is a valid reason; let the early v2.4-series be witness to why
> this is a good stance.
David,
I've must install Linux on AMD386 DX40, HD Maxtor 160MB, 8MB RAM for
this task i used kernel 2.0.39.
When I compiled kernel 2.0.39, I noticed some `warnings` which I
corrected as mentioned previously.
Then I inspected the VM subsystem code, where found any stuff
that could be cleanup and improved, such as:
+#define clear_page(page) memset((void *)(page), 0, PAGE_SIZE)
+#define copy_page(to,from) memcpy((void *)(to), (void *)(from),
PAGE_SIZE)
> Speedups are generally not counted as a valid reason, unless we're
> talking a change in the order of a magnitude or more. Code cleanup
> might be a good reason, but then I'll merge it into the 2.0.41-tree
> instead; this will probably be the case for your lxdialog-fixes, since
> I'm cleaning up that code anyway for 2.0.41.
LOL!
The main reason this patch is cleanup and better code standartize.
I think thats code cleanup is good reason too!
> Regards: David Weinehall
> --
> /> David Weinehall <tao@acc.umu.se> /> Northern lights wander <\
> // Maintainer of the v2.0 kernel // Dance across the winter sky //
> \> http://www.acc.umu.se/~tao/ </ Full colour fire </
>
Have fun!
--
Fernando Alencar Maróstica
Graduate Student, Computer Science
Linux Register User Id #281457
University Methodist of Piracicaba
Departament of Computer Science
home: http://www.unimep.br/~famarost
prev parent reply other threads:[~2002-10-21 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1034548634.543.1.camel@nitrogenium>
[not found] ` <20021014220527.GU26715@khan.acc.umu.se>
2002-10-15 15:37 ` [PATCH 2.0] Fixed kernel stuff Fernando Alencar Maróstica
2002-10-15 19:02 ` Fernando Alencar Maróstica
2002-10-15 21:11 ` David Weinehall
2002-10-21 19:49 ` Fernando Alencar Maróstica [this message]
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=1035229745.625.0.camel@nitrogenium \
--to=famarost@unimep.br \
--cc=linux-kernel@vger.kernel.org \
--cc=tao@acc.umu.se \
/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