linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: linux-kernel <linux-kernel@vger.rutgers.edu>
Cc: linux-mm <linux-mm@kvack.org>
Subject: [PATCH *] vhand-2.1.65b released
Date: Thu, 20 Nov 1997 10:57:51 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.3.91.971120105420.12363B-100000@mirkwood.dummy.home> (raw)

Hi there,

since so many people have found something wrong with vhand-2.1.6[45]
(particularly the CPU usage), I have implemented their ideas and
I've made the 'anti-fragmentation' unit even more agressive, since
some people still reported crashes because of memory fragmentation...

You can get the patch at:
<a href="www.fys.ruu.nl/~riel/">my homepage</a>.

happy hacking,

Rik.

----------
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...

             reply	other threads:[~1997-11-20 17:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-20  9:57 Rik van Riel [this message]
1997-11-20 22:54 ` Mathieu Guillaume
     [not found] <19971120152522.39483@helix.caltech.edu>
1997-11-21  1:37 ` 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=Pine.LNX.3.91.971120105420.12363B-100000@mirkwood.dummy.home \
    --to=h.h.vanriel@fys.ruu.nl \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    /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