public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Hoogerhuis <alexh@ihatent.com>
To: Martin Knoblauch <Martin.Knoblauch@TeraPort.de>
Cc: jason@topic.com.au,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [OT?] Re: [PATCH] patch's for vmware 2.0.4 for use with linux-2.4.8 kernel
Date: 18 Aug 2001 12:09:37 +0200	[thread overview]
Message-ID: <m3ofpd3cim.fsf@lapper.ihatent.com> (raw)
In-Reply-To: <3B7D1846.BEB929DE@TeraPort.de>
In-Reply-To: <3B7D1846.BEB929DE@TeraPort.de>

Martin Knoblauch <Martin.Knoblauch@TeraPort.de> writes:

> > [PATCH] patch's for vmware 2.0.4 for use with linux-2.4.8 kernel
> > 
> > From: Jason Thomas (jason@topic.com.au)
> > Date: Thu Aug 16 2001 - 03:49:38 EST
> > 
> > 
> > attached are two very small patches for those that want them. they make
> > vmware's kernel modules compile with 2.4.8. Its not all my work, its a
> > combination of what was posted a while back and my work.
> > 
> Jason,
> 
>  a small gotcha in your vmmon patch. You moved up hostif.h in driver.c,
> but you forgot to remove the original include. See my attached new
> version of the patch.
> 
> Martin
> -- 

I've applied the patch with your fixes, and I've always noticed that
VMware seem to leak a bit of memory (occording to top and ps). Running
with 128Mb in a Win2k box it started off at 161Mb process size (140Mb
RSS) and within 5 minutes it had turned into 203Mb process size (still
only 140Mb RSS). Have anyone seen similar behavior, and does anyone
have any pointers to where I can find more info on it?

mvh,
A
-- 
Alexander Hoogerhuis
FYI: perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'

  reply	other threads:[~2001-08-18 10:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-17 13:12 [PATCH] patch's for vmware 2.0.4 for use with linux-2.4.8 kernel Martin Knoblauch
2001-08-18 10:09 ` Alexander Hoogerhuis [this message]
2001-08-20  6:36   ` [OT?] " Martin Knoblauch

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=m3ofpd3cim.fsf@lapper.ihatent.com \
    --to=alexh@ihatent.com \
    --cc=Martin.Knoblauch@TeraPort.de \
    --cc=jason@topic.com.au \
    --cc=linux-kernel@vger.kernel.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