linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: Eugene Crosser <crosser@average.org>
Cc: linux-kernel <linux-kernel@vger.rutgers.edu>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: vhand-2.1.64... problems solved - but not all ;)
Date: Thu, 20 Nov 1997 10:00:52 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.3.91.971120095338.11037A-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <64vsjf$aq@pccross.average.org>

On 19 Nov 1997, Eugene Crosser wrote:

> just to let you know.  For me, all 2.1.xx kernels are hanging trying
> to allocate TCP buffers (I reported this problem), and I tried vhand
> patch in the hope that it may help, as it deals with memory management.

It's still in beta :)
> 
> Unfortunately, it did not.  I got the system hung with the same
> symptoms in less then 24 hours uptime.  Also, perfomance of cpu
> intensive applications (mpg123) dropped noticably with vhand.

I'm working on that one, and it seems like Joe Fouch has given
me the 'golden hint' on what to do. So I implemented his idea
and tested... It improved performance in CPU intensive applications,
but I/O intensive stuff really suffers.
In vhand-2.1.66 this should be better...
> 
> I have a 120MHz 486dx4 w/16Mb, kernel 2.1.63+vhand-2.1.63.
> 
> BTW, Zlatko's patch seemed to cure the hang problem, but after a few
> days, the system freezed anyway at the same place.

Hmmm, could you give me some more details:
- type of network card
- amount of network-buffers allocated each second (!)
- size of allocated network buffers
- amount of swapping/paging going on
- how was the CPU usage of kswapd/vhand during that time?

thanks and good luck,

Rik.

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

           reply	other threads:[~1997-11-20 13:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <64vsjf$aq@pccross.average.org>]

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.971120095338.11037A-100000@mirkwood.dummy.home \
    --to=h.h.vanriel@fys.ruu.nl \
    --cc=crosser@average.org \
    --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