linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* Re: vhand-2.1.64... problems solved - but not all ;)
       [not found] <64vsjf$aq@pccross.average.org>
@ 1997-11-20  9:00 ` Rik van Riel
  0 siblings, 0 replies; only message in thread
From: Rik van Riel @ 1997-11-20  9:00 UTC (permalink / raw)
  To: Eugene Crosser; +Cc: linux-kernel, linux-mm

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...

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~1997-11-20 13:14 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <64vsjf$aq@pccross.average.org>
1997-11-20  9:00 ` vhand-2.1.64... problems solved - but not all ;) Rik van Riel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox