Re: Break 2.4 VM in five easy steps

2001-06-12 Thread Bernd Jendrissek
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jun 11, 2001 at 04:04:45PM -0300, Rik van Riel wrote: > On Mon, 11 Jun 2001, Maciej Zenczykowski wrote: > > On Fri, 8 Jun 2001, Pavel Machek wrote: > > > > > That modulo is likely slower than dereference. > > > > > > > + if (coun

Re: Break 2.4 VM in five easy steps

2001-06-11 Thread Rik van Riel
On Mon, 11 Jun 2001, Maciej Zenczykowski wrote: > On Fri, 8 Jun 2001, Pavel Machek wrote: > > > That modulo is likely slower than dereference. > > > > > + if (count % 256 == 0) { > > You are forgetting that this case should be converted to and 255 > or a plain byte reference by any o

Re: Break 2.4 VM in five easy steps

2001-06-11 Thread Maciej Zenczykowski
On Fri, 8 Jun 2001, Pavel Machek wrote: > That modulo is likely slower than dereference. > > > + if (count % 256 == 0) { You are forgetting that this case should be converted to and 255 or a plain byte reference by any optimizing compiler - and gcc surely is, on x86 this code can b

Re: Break 2.4 VM in five easy steps

2001-06-11 Thread Pavel Machek
Hi! > If this solves your problem, use it; if your name is Linus or Alan, > ignore or do it right please. Well I guess you should do CONDITIONAL_SCHEDULE (if it is not defined as macro, do if (current->need_resched) schedule()). That modulo is likely slower than dereference. > diff -u -r1.1 -r

Re: Break 2.4 VM in five easy steps

2001-06-11 Thread Pavel Machek
Hi! > But if the page in memory is 'dirty', you can't be efficient with swapping > *in* the page. The page on disk is invalid and should be released, or am I > missing something? Yes. You are missing fragmentation. This keeps it low.

Re: Break 2.4 VM in five easy steps

2001-06-10 Thread Rob Landley
>I realize that assembly is platform-specific. Being >that I use the IA32 class machine, that's what I >would write for. Others who use other platforms could >do the deed for their native language. Meaning we'd still need a good C implementation anyway for the 75% of platforms nobody's going to

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-09 Thread Zlatko Calusic
Mike Galbraith <[EMAIL PROTECTED]> writes: > On Fri, 8 Jun 2001, John Stoffel wrote: > > > Mike> OK, riddle me this. If this test is a crummy test, just how is > > Mike> it that I was able to warn Rik in advance that when 2.4.5 was > > Mike> released, he should expect complaints? How did I _k

Re: Break 2.4 VM in five easy steps

2001-06-09 Thread Mike A. Harris
On Sat, 9 Jun 2001, Rik van Riel wrote: >> Why are half the people here trying to hide behind this diskspace >> is cheap argument? If we rely on that, then Linux sucks shit. > >Never mind them, I haven't seen any of them contribute >VM code, even ;) Nor have I, but I think you guys working on i

Re: Break 2.4 VM in five easy steps

2001-06-09 Thread Rik van Riel
On Wed, 6 Jun 2001, Mike A. Harris wrote: > Why are half the people here trying to hide behind this diskspace > is cheap argument? If we rely on that, then Linux sucks shit. Never mind them, I haven't seen any of them contribute VM code, even ;) OTOH, disk space _is_ cheap, so the other VM - p

Re: Break 2.4 VM in five easy steps

2001-06-09 Thread Rik van Riel
On 6 Jun 2001, Eric W. Biederman wrote: > Derek Glidden <[EMAIL PROTECTED]> writes: > > > The problem I reported is not that 2.4 uses huge amounts of swap but > > that trying to recover that swap off of disk under 2.4 can leave the > > machine in an entirely unresponsive state, while 2.2 handles

Re: Break 2.4 VM in five easy steps

2001-06-09 Thread Rik van Riel
On Wed, 6 Jun 2001, Derek Glidden wrote: > Or are you saying that if someone is unhappy with a particular > situation, they should just keep their mouth shut and accept it? There are lots of options ... 1) wait until somebody fixes the problem 2) fix the problem yourself 3) start infinite flame

Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Rik van Riel
On Wed, 6 Jun 2001, Sean Hunter wrote: > A working VM would have several differences from what we have in my > opinion, among which are: > - It wouldn't require 8GB of swap on my large boxes > - It wouldn't suffer from the "bounce buffer" bug on my > large boxes >

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Mark Hahn
> reads the RTC device. The patched RTC driver can then > measure the elapsed time between the interrupt and the > read from userspace. Voila: latency. interesting, but I'm not sure there's much advantage over doing it entirely in user-space with the normal /dev/rtc: http://brain.mcmas

Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Mike A. Harris
On 6 Jun 2001, Miles Lane wrote: >> Precicely. Saying 8x RAM doesn't change it either. Sometime >> next week I'm going to purposefully put a new 60Gb disk in on a >> separate controller as pure swap on top of 256Mb of RAM. My >> guess is after bootup, and login, I'll have 48Gb of stuff in >> s

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Mike Galbraith
On Sat, 9 Jun 2001, Jonathan Morton wrote: > >> On the subject of Mike Galbraith's kernel compilation test, how much > >> physical RAM does he have for his machine, what type of CPU is it, and what > >> (approximate) type of device does he use for swap? I'll see if I can > >> partially duplicate

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Mike Galbraith
On Fri, 8 Jun 2001, Marcelo Tosatti wrote: > On Fri, 8 Jun 2001, John Stoffel wrote: > > > More importantly, a *repeatable* set of tests is what is needed to > > test the VM and get consistent results from run to run, so you can see > > how your changes are impacting performance. The kernel comp

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Mike Galbraith
On Fri, 8 Jun 2001, Tobias Ringstrom wrote: > On Fri, 8 Jun 2001, Mike Galbraith wrote: > > On Fri, 8 Jun 2001, Tobias Ringstrom wrote: > > > On Fri, 8 Jun 2001, Mike Galbraith wrote: > > > > I gave this a shot at my favorite vm beater test (make -j30 bzImage) > > > > while testing some other stu

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Jonathan Morton
>> On the subject of Mike Galbraith's kernel compilation test, how much >> physical RAM does he have for his machine, what type of CPU is it, and what >> (approximate) type of device does he use for swap? I'll see if I can >> partially duplicate his results at this end. So far all my tests have

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Mike Galbraith
On Sat, 9 Jun 2001, Jonathan Morton wrote: > On the subject of Mike Galbraith's kernel compilation test, how much > physical RAM does he have for his machine, what type of CPU is it, and what > (approximate) type of device does he use for swap? I'll see if I can > partially duplicate his results

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Rik van Riel
On Fri, 8 Jun 2001, Mike Galbraith wrote: > On Fri, 8 Jun 2001, John Stoffel wrote: > > I agree, this isn't really a good test case. I'd rather see what > > happens when you fire up a gimp session to edit an image which is > > *almost* the size of RAM, or even just 50% the size of ram. > > OK,

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Andrew Morton
Jonathan Morton wrote: > > [ Re-entering discussion after too long a day and a long sleep... ] > > >> There is the problem in terms of some people want pure interactive > >> performance, while others are looking for throughput over all else, > >> but those are both extremes of the spectrum. Tho

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Jonathan Morton
[ Re-entering discussion after too long a day and a long sleep... ] >> There is the problem in terms of some people want pure interactive >> performance, while others are looking for throughput over all else, >> but those are both extremes of the spectrum. Though I suspect >> raw throughput is t

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Marcelo Tosatti
On Fri, 8 Jun 2001, John Stoffel wrote: > > Marcelo> Now the stock kernel gives us crappy interactivity compared > Marcelo> to my patch. (Note: my patch still does not gives me the > Marcelo> interactivity I want under high VM loads, but I hope to get > Marcelo> there soon). > > This raises t

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread John Stoffel
Marcelo> Now the stock kernel gives us crappy interactivity compared Marcelo> to my patch. (Note: my patch still does not gives me the Marcelo> interactivity I want under high VM loads, but I hope to get Marcelo> there soon). This raises the important question, how can we objectively measure in

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Marcelo Tosatti
On Fri, 8 Jun 2001, John Stoffel wrote: > > Mike> OK, riddle me this. If this test is a crummy test, just how is > Mike> it that I was able to warn Rik in advance that when 2.4.5 was > Mike> released, he should expect complaints? How did I _know_ that? > Mike> The answer is that I fiddle with

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Tobias Ringstrom
On Fri, 8 Jun 2001, Mike Galbraith wrote: > On Fri, 8 Jun 2001, Tobias Ringstrom wrote: > > On Fri, 8 Jun 2001, Mike Galbraith wrote: > > > I gave this a shot at my favorite vm beater test (make -j30 bzImage) > > > while testing some other stuff today. > > > > Could you please explain what is good

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Mike Galbraith
On Fri, 8 Jun 2001, John Stoffel wrote: > Mike> OK, riddle me this. If this test is a crummy test, just how is > Mike> it that I was able to warn Rik in advance that when 2.4.5 was > Mike> released, he should expect complaints? How did I _know_ that? > Mike> The answer is that I fiddle with Rik

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread John Stoffel
Mike> OK, riddle me this. If this test is a crummy test, just how is Mike> it that I was able to warn Rik in advance that when 2.4.5 was Mike> released, he should expect complaints? How did I _know_ that? Mike> The answer is that I fiddle with Rik's code a lot, and I test Mike> with this test b

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Mike Galbraith
On Fri, 8 Jun 2001, John Stoffel wrote: > > "Tobias" == Tobias Ringstrom <[EMAIL PROTECTED]> writes: > > Tobias> On Fri, 8 Jun 2001, Mike Galbraith wrote: > > >> I gave this a shot at my favorite vm beater test (make -j30 bzImage) > >> while testing some other stuff today. > > Tobias> Could y

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Mike Galbraith
On Fri, 8 Jun 2001, Tobias Ringstrom wrote: > On Fri, 8 Jun 2001, Mike Galbraith wrote: > > I gave this a shot at my favorite vm beater test (make -j30 bzImage) > > while testing some other stuff today. > > Could you please explain what is good about this test? I understand that > it will stress

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread John Stoffel
> "Tobias" == Tobias Ringstrom <[EMAIL PROTECTED]> writes: Tobias> On Fri, 8 Jun 2001, Mike Galbraith wrote: >> I gave this a shot at my favorite vm beater test (make -j30 bzImage) >> while testing some other stuff today. Tobias> Could you please explain what is good about this test? I Tob

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Tobias Ringstrom
On Fri, 8 Jun 2001, Mike Galbraith wrote: > I gave this a shot at my favorite vm beater test (make -j30 bzImage) > while testing some other stuff today. Could you please explain what is good about this test? I understand that it will stress the VM, but will it do so in a realistic and relevant w

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Mike Galbraith
On Fri, 8 Jun 2001, Jonathan Morton wrote: > http://www.chromatix.uklinux.net/linux-patches/vm-update-2.patch > > Try this. I can't guarantee it's SMP-safe yet (I'm leaving the gurus to > that, but they haven't told me about any errors in the past hour so I'm > assuming they aren't going to find

Re: Break 2.4 VM in five easy steps

2001-06-08 Thread Bernd Jendrissek
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jun 07, 2001 at 03:38:35PM -0600, Brian D Heaton wrote: > Maybe i'm missing something. I just tried this (with the 262144k/1 > and 128k/2048 params) and my results are within .1s of each other. This is > without any special patches. A

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread C. Martins
In my everyday desktop workstation (PII 350) I have 64MB of RAM and use 300MB of swap, 150MB on each hard disk. After upgrading to 2.4, and maintaining the same set of applications (KDE, Netscape & friends), the machine performance is _definitely_ much worse, in terms of responsiveness and

Re: VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Jonathan Morton
At 12:29 am +0100 8/6/2001, Shane Nay wrote: >(VM report at Marcelo Tosatti's request. He has mentioned that rather than >complaining about the VM that people mention what there experiences were. I >have tried to do so in the way that he asked.) >> By performance you mean interactivity or throu

VM Report was:Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Shane Nay
(VM report at Marcelo Tosatti's request. He has mentioned that rather than complaining about the VM that people mention what there experiences were. I have tried to do so in the way that he asked.) > 1) Describe what you're running. (your workload) A lot of daemons, all on a private network

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Marcelo Tosatti
On Thu, 7 Jun 2001, Shane Nay wrote: > On Thursday 07 June 2001 13:00, Marcelo Tosatti wrote: > > On Thu, 7 Jun 2001, Shane Nay wrote: > > > (Oh, BTW, I really appreciate the work that people have done on the VM, > > > but folks that are just talking..., well, think clearly before you impact >

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread LA Walsh
"Eric W. Biederman" wrote: > LA Walsh <[EMAIL PROTECTED]> writes: > > > Now for whatever reason, since 2.4, I consistently use at least > > a few Mb of swap -- stands at 5Meg now. Weird -- but I notice things > > like nscd running 7 copies that take 72M. Seems like overkill for > > a laptop

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Shane Nay
Uh, last I checked on my linux based embedded device I didn't want to swap to flash. Hmm.., now why was that..., oh, that's right, it's *much* more expensive than memory, oh yes, and it actually gets FRIED when you write to a block more than 100k times. Oh, what was that other thing..., oh ye

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Shane Nay
On Thursday 07 June 2001 13:00, Marcelo Tosatti wrote: > On Thu, 7 Jun 2001, Shane Nay wrote: > > (Oh, BTW, I really appreciate the work that people have done on the VM, > > but folks that are just talking..., well, think clearly before you impact > > other people that are writing code.) > > If al

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Marcelo Tosatti
On Thu, 7 Jun 2001, Shane Nay wrote: > (Oh, BTW, I really appreciate the work that people have done on the VM, but > folks that are just talking..., well, think clearly before you impact other > people that are writing code.) If all the people talking were reporting results we would be reall

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Miles Lane
On 07 Jun 2001 11:49:47 -0400, Derek Glidden wrote: > Miles Lane wrote: > > > > So please, if you have new facts that you want to offer that > > will help us characterize and understand these VM issues better > > or discover new problems, feel free to share them. But if you > > just want to rant

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Marcelo Tosatti
On Thu, 7 Jun 2001, Mike Galbraith wrote: > On 6 Jun 2001, Eric W. Biederman wrote: > > > Mike Galbraith <[EMAIL PROTECTED]> writes: > > > > > > If you could confirm this by calling swapoff sometime other than at > > > > reboot time. That might help. Say by running top on the console. > > >

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread José Luis Domingo López
On Thursday, 07 June 2001, at 09:23:42 +0200, Helge Hafting wrote: > Derek Glidden wrote: > > > > Helge Hafting wrote: > [...] > The machine froze 10 seconds or so at the end of the minute, I can > imagine that biting with bigger swap. > Same behavior here with a Pentium III 600, 128 MB RAM and

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Eric W. Biederman
Helge Hafting <[EMAIL PROTECTED]> writes: > A problem with this is that normal paging-in is allowed to page other > things out as well. But you can't have that when swap is about to > be turned off. My guess is that swapoff functionality was perceived to > be so seldom used that they didn't bot

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Eric W. Biederman
LA Walsh <[EMAIL PROTECTED]> writes: > Now for whatever reason, since 2.4, I consistently use at least > a few Mb of swap -- stands at 5Meg now. Weird -- but I notice things > like nscd running 7 copies that take 72M. Seems like overkill for > a laptop. So the question becomes why you are

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Derek Glidden
Miles Lane wrote: > > So please, if you have new facts that you want to offer that > will help us characterize and understand these VM issues better > or discover new problems, feel free to share them. But if you > just want to rant, I, for one, would rather you didn't. *sigh* Not to prolong a

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Mike Galbraith
On Thu, 7 Jun 2001, Bulent Abali wrote: > I happened to saw this one with debugger attached serial port. > The system was alive. I think I was watching the free page count and > it was decreasing very slowly may be couple pages per second. Bigger > the swap usage longer it takes to do swapoff.

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread LA Walsh
"Eric W. Biederman" wrote: > There are cetain scenario's where you can't avoid virtual mem = > min(RAM,swap). Which is what I was trying to say, (bad formula). What > happens is that pages get referenced evenly enough and quickly enough > that you simply cannot reuse the on disk pages. Basical

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Bulent Abali
>> O.k. I think I'm ready to nominate the dead swap pages for the big >> 2.4.x VM bug award. So we are burning cpu cycles in sys_swapoff >> instead of being IO bound? Just wanting to understand this the cheap way :) > >There's no IO being done whatsoever (that I can see with only a blinky). >

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Bernd Jendrissek
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 NotDashEscaped: You need GnuPG to verify this message First things first: 1) Please Cc: me when responding, 2) apologies for dropping any References: headers, 3) sorry for bad formatting "Jeffrey W. Baker" wrote: > On Tue, 5 Jun 2001, Derek Glidden w

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Eric W. Biederman
Linus Torvalds <[EMAIL PROTECTED]> writes: > On 7 Jun 2001, Eric W. Biederman wrote: > > No - I suspect that we're not actually doing all that much IO at all, and > the real reason for the lock-up is just that the current algorithm is so > bad that when it starts to act exponentially worse it re

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Mike Galbraith
On 7 Jun 2001, Eric W. Biederman wrote: > Mike Galbraith <[EMAIL PROTECTED]> writes: > > > On 7 Jun 2001, Eric W. Biederman wrote: > > > > > Does this improve the swapoff speed or just allow other programs to > > > run at the same time? If it is still slow under that kind of load it > > > would

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Linus Torvalds
On 7 Jun 2001, Eric W. Biederman wrote: > [EMAIL PROTECTED] (Linus Torvalds) writes: > > > > Somebody interested in trying the above add? And looking for other more > > obvious bandaid fixes. It won't "fix" swapoff per se, but it might make > > it bearable and bring it to the 2.2.x levels. >

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Eric W. Biederman
Mike Galbraith <[EMAIL PROTECTED]> writes: > On 7 Jun 2001, Eric W. Biederman wrote: > > > Does this improve the swapoff speed or just allow other programs to > > run at the same time? If it is still slow under that kind of load it > > would be interesting to know what is taking up all time. >

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Eric W. Biederman
[EMAIL PROTECTED] (Linus Torvalds) writes: > > Somebody interested in trying the above add? And looking for other more > obvious bandaid fixes. It won't "fix" swapoff per se, but it might make > it bearable and bring it to the 2.2.x levels. At little bit. The one really bad behavior of not le

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Mike Galbraith
On 7 Jun 2001, Eric W. Biederman wrote: > Mike Galbraith <[EMAIL PROTECTED]> writes: > > > On 6 Jun 2001, Eric W. Biederman wrote: > > > > > Mike Galbraith <[EMAIL PROTECTED]> writes: > > > > > > > > If you could confirm this by calling swapoff sometime other than at > > > > > reboot time. That

Re: Break 2.4 VM in five easy steps

2001-06-07 Thread Helge Hafting
Derek Glidden wrote: > > Helge Hafting wrote: > > > > The drive is inactive because it isn't needed, the machine is > > running loops on data in memory. And it is unresponsive because > > nothing else is scheduled, maybe "swapoff" is easier to implement > > I don't quite get what you're saying.

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Eric W. Biederman
Mike Galbraith <[EMAIL PROTECTED]> writes: > On 6 Jun 2001, Eric W. Biederman wrote: > > > Mike Galbraith <[EMAIL PROTECTED]> writes: > > > > > > If you could confirm this by calling swapoff sometime other than at > > > > reboot time. That might help. Say by running top on the console. > > > >

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Eric W. Biederman
LA Walsh <[EMAIL PROTECTED]> writes: > "Eric W. Biederman" wrote: > > > The hard rule will always be that to cover all pathological cases swap > > must be greater than RAM. Because in the worse case all RAM will be > > in thes swap cache. That this is more than just the worse case in 2.4 > > i

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Mike Galbraith
On 6 Jun 2001, Eric W. Biederman wrote: > Mike Galbraith <[EMAIL PROTECTED]> writes: > > > > If you could confirm this by calling swapoff sometime other than at > > > reboot time. That might help. Say by running top on the console. > > > > The thing goes comatose here too. SCHED_RR vmstat doesn

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Miles Lane
On 06 Jun 2001 20:34:49 -0400, Mike A. Harris wrote: > On Wed, 6 Jun 2001, Derek Glidden wrote: > > >> Derek> overwhelmed. On the system I'm using to write this, with > >> Derek> 512MB of RAM and 512MB of swap, I run two copies of this > >> > >> Please see the following message on the kernel m

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Mike A. Harris
On Wed, 6 Jun 2001, Derek Glidden wrote: >> Derek> overwhelmed. On the system I'm using to write this, with >> Derek> 512MB of RAM and 512MB of swap, I run two copies of this >> >> Please see the following message on the kernel mailing list, >> >> 3086:Linus 2.4.0 notes are quite clear that yo

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Mike A. Harris
On Wed, 6 Jun 2001, android wrote: >associated with that mindset that made Microsoft such a [fill in the blank]. >As for the 2.4 VM problem, what are you doing with your machine that's >making it use up so much memory? I have several processes running >on mine all the time, including a slew in X,

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Mike A. Harris
On Wed, 6 Jun 2001, Dr S.M. Huen wrote: >> For large memory boxes, this is ridiculous. Should I have 8GB of swap? >> > >Do I understand you correctly? >ECC grade SDRAM for your 8GB server costs £335 per GB as 512MB sticks even >at today's silly prices (Crucial). Ultra160 SCSI costs £8.93/GB as 7

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Kai Henningsen
[EMAIL PROTECTED] (Alexander Viro) wrote on 06.06.01 in <[EMAIL PROTECTED]>: > On Wed, 6 Jun 2001, Sean Hunter wrote: > > > This is completely bogus. I am not saying that I can't afford the swap. > > What I am saying is that it is completely broken to require this amount > > of swap given the b

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Jonathan Morton
At 11:27 pm +0100 6/6/2001, android wrote: >> >I'd be happy to write a new routine in assembly >> >>I sincerely hope you're joking. >> >>It's the algorithm that needs fixing, not the implementation of that >>algorithm. Writing in assembler? Hope you're proficient at writing in >>x86, PPC, 68k, M

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Robert Love
On 06 Jun 2001 15:27:57 -0700, android wrote: > >I sincerely hope you're joking. > > I realize that assembly is platform-specific. Being that I use the IA32 class > machine, that's what I would write for. Others who use other platforms could > do the deed for their native language. no, look at th

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Antoine
hi, I have a problem with kswapd, it takes suddenly 98 % CPU and crash my server I dono why, I have a linux kernel 2.2.17 debian distro if anyone can help me ... thx ;) Antoine - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread android
> >I'd be happy to write a new routine in assembly > >I sincerely hope you're joking. > >It's the algorithm that needs fixing, not the implementation of that >algorithm. Writing in assembler? Hope you're proficient at writing in >x86, PPC, 68k, MIPS (several varieties), ARM, SPARC, and whatever

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Jonathan Morton
>I'd be happy to write a new routine in assembly I sincerely hope you're joking. It's the algorithm that needs fixing, not the implementation of that algorithm. Writing in assembler? Hope you're proficient at writing in x86, PPC, 68k, MIPS (several varieties), ARM, SPARC, and whatever other ar

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread LA Walsh
"Eric W. Biederman" wrote: > The hard rule will always be that to cover all pathological cases swap > must be greater than RAM. Because in the worse case all RAM will be > in thes swap cache. That this is more than just the worse case in 2.4 > is problematic. I.e. In the worst case: > Virtual

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread android
>Is anybody interested in making "swapoff()" better? Please speak up.. > > Linus I'd be happy to write a new routine in assembly, if I had a clue as to how the VM algorithm works in Linux. What should swapoff do if all physical memory is in use? How does the swapping algorithm b

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Linus Torvalds
In article <[EMAIL PROTECTED]>, Derek Glidden <[EMAIL PROTECTED]> wrote: > >After reading the messages to this list for the last couple of weeks and >playing around on my machine, I'm convinced that the VM system in 2.4 is >still severely broken. Now, this may well be true, but what you actual

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Daniel Phillips
On Wednesday 06 June 2001 20:27, Eric W. Biederman wrote: > The hard rule will always be that to cover all pathological cases > swap must be greater than RAM. Because in the worse case all RAM > will be in thes swap cache. Could you explain in very simple terms how the worst case comes about? -

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Derek Glidden
Mike Galbraith wrote: > > Can you try the patch below to see if it helps? If you watch > with vmstat, you should see swap shrinking after your test. > Let is shrink a while and then see how long swapoff takes. > Under a normal load, it'll munch a handfull of them at least > once a second and kee

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Eric W. Biederman
Mike Galbraith <[EMAIL PROTECTED]> writes: > On 6 Jun 2001, Eric W. Biederman wrote: > > > Derek Glidden <[EMAIL PROTECTED]> writes: > > > > > > > The problem I reported is not that 2.4 uses huge amounts of swap but > > > that trying to recover that swap off of disk under 2.4 can leave the > > >

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Derek Glidden
"Eric W. Biederman" wrote: > > Derek Glidden <[EMAIL PROTECTED]> writes: > > > The problem I reported is not that 2.4 uses huge amounts of swap but > > that trying to recover that swap off of disk under 2.4 can leave the > > machine in an entirely unresponsive state, while 2.2 handles identical

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Mike Galbraith
On 6 Jun 2001, Eric W. Biederman wrote: > Derek Glidden <[EMAIL PROTECTED]> writes: > > > > The problem I reported is not that 2.4 uses huge amounts of swap but > > that trying to recover that swap off of disk under 2.4 can leave the > > machine in an entirely unresponsive state, while 2.2 handle

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread android
>Furthermore, I am not demanding anything, much less "priority fixing" >for this bug. Its my personal opinion that this is the most critical bug >in the 2.4 series, and if I had the time and skill, this is what I would >be working on. Because I don't have the time and skill, I am perfectly >happy

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Mike Galbraith
On Tue, 5 Jun 2001, Derek Glidden wrote: > After reading the messages to this list for the last couple of weeks and > playing around on my machine, I'm convinced that the VM system in 2.4 is > still severely broken. ... Hi, Can you try the patch below to see if it helps? If you watch with vms

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Eric W. Biederman
Derek Glidden <[EMAIL PROTECTED]> writes: > The problem I reported is not that 2.4 uses huge amounts of swap but > that trying to recover that swap off of disk under 2.4 can leave the > machine in an entirely unresponsive state, while 2.2 handles identical > situations gracefully. > The inte

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Mark Salisbury
On Wed, 06 Jun 2001, Dr S.M. Huen wrote: > The whole screaming match is about whether a drastic degradation on using > swap with less than the 2*RAM swap specified by the developers should lead > one to conclude that a kernel is "broken". I would argue that any system that performs substantially

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Derek Glidden
"Eric W. Biederman" wrote: > > > Or are you saying that if someone is unhappy with a particular > > situation, they should just keep their mouth shut and accept it? > > It's worth complaining about. It is also worth digging into and find > out what the real problem is. I have a hunch that this

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Dr S.M. Huen
On Wed, 6 Jun 2001, Kurt Roeckx wrote: > On Wed, Jun 06, 2001 at 10:57:57AM +0100, Dr S.M. Huen wrote: > > On Wed, 6 Jun 2001, Sean Hunter wrote: > > > > > > > > For large memory boxes, this is ridiculous. Should I have 8GB of swap? > > > > > > > Do I understand you correctly? > > ECC grade

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Eric W. Biederman
Derek Glidden <[EMAIL PROTECTED]> writes: > John Alvord wrote: > > > > On Wed, 06 Jun 2001 11:31:28 -0400, Derek Glidden > > <[EMAIL PROTECTED]> wrote: > > > > > > > >I'm beginning to be amazed at the Linux VM hackers' attitudes regarding > > >this problem. I expect this sort of behaviour from

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread José Luis Domingo López
On Wednesday, 06 June 2001, at 10:19:30 +0200, Xavier Bestel wrote: > On 05 Jun 2001 23:19:08 -0400, Derek Glidden wrote: > > On Wed, Jun 06, 2001 at 12:16:30PM +1000, Andrew Morton wrote: > [...] > Did you try to put twice as much swap as you have RAM ? (e.g. add a 512M > swapfile to your box) >

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Kurt Roeckx
On Wed, Jun 06, 2001 at 10:57:57AM +0100, Dr S.M. Huen wrote: > On Wed, 6 Jun 2001, Sean Hunter wrote: > > > > > For large memory boxes, this is ridiculous. Should I have 8GB of swap? > > > > Do I understand you correctly? > ECC grade SDRAM for your 8GB server costs £335 per GB as 512MB stick

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Remi Turk
On Wed, Jun 06, 2001 at 06:48:32AM -0400, Alexander Viro wrote: > On Wed, 6 Jun 2001, Sean Hunter wrote: > > > This is completely bogus. I am not saying that I can't afford the swap. > > What I am saying is that it is completely broken to require this amount > > of swap given the boundaries of ef

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread dean gaudet
On Wed, 6 Jun 2001, Alexander Viro wrote: > On Wed, 6 Jun 2001, Sean Hunter wrote: > > > This is completely bogus. I am not saying that I can't afford the swap. > > What I am saying is that it is completely broken to require this amount > > of swap given the boundaries of efficient use. > > Funny

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Jeffrey W. Baker
On 6 Jun 2001, Eric W. Biederman wrote: > "Jeffrey W. Baker" <[EMAIL PROTECTED]> writes: > > > On Tue, 5 Jun 2001, Derek Glidden wrote: > > > > > > > > After reading the messages to this list for the last couple of weeks and > > > playing around on my machine, I'm convinced that the VM system in

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread dean gaudet
On Wed, 6 Jun 2001, Dr S.M. Huen wrote: > If you can afford 4GB RAM, you certainly can afford 8GB swap. this is a completely crap argument. you should study the economics of managing a farm of thousands of machines some day. when you do this, you'll also learn to consider the power requirement

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Ben Greear
Richard Gooch wrote: > > Daniel Phillips writes: > > On Wednesday 06 June 2001 10:54, Sean Hunter wrote: > > > > > > Did you try to put twice as much swap as you have RAM ? (e.g. add a > > > > 512M swapfile to your box) > > > > This is what Linus recommended for 2.4 (swap = 2 * RAM), saying > > >

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Derek Glidden
John Alvord wrote: > > On Wed, 06 Jun 2001 11:31:28 -0400, Derek Glidden > <[EMAIL PROTECTED]> wrote: > > > > >I'm beginning to be amazed at the Linux VM hackers' attitudes regarding > >this problem. I expect this sort of behaviour from academics - ignoring > >real actual problems being reporte

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread John Alvord
On Wed, 06 Jun 2001 11:31:28 -0400, Derek Glidden <[EMAIL PROTECTED]> wrote: > >I'm beginning to be amazed at the Linux VM hackers' attitudes regarding >this problem. I expect this sort of behaviour from academics - ignoring >real actual problems being reported by real actual people really and

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Christian Bornträger
OK, Linus said if I use swap it should be at least twice as much as RAM. there will be much more discussion about it, for me this contraint is a very very bad idea. Have you ever thought about diskless workstations? Swapping over a network sounds ugly. Nevertheless, my question is: what happens

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Derek Glidden
> Funny. I can count many ways in which 4.3BSD, SunOS{3,4} and post-4.4 BSD > systems I've used were broken, but I've never thought that swap==2*RAM rule > was one of them. Yes, but Linux isn't 4.3BSD, SunOS or post-4.4 BSD. Not to mention, all other OS's I've had experience using *don't* break

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Richard Gooch
Daniel Phillips writes: > On Wednesday 06 June 2001 10:54, Sean Hunter wrote: > > > > Did you try to put twice as much swap as you have RAM ? (e.g. add a > > > 512M swapfile to your box) > > > This is what Linus recommended for 2.4 (swap = 2 * RAM), saying > > > that anything less won't do any go

Re: Break 2.4 VM in five easy steps

2001-06-06 Thread Derek Glidden
Helge Hafting wrote: > > The drive is inactive because it isn't needed, the machine is > running loops on data in memory. And it is unresponsive because > nothing else is scheduled, maybe "swapoff" is easier to implement I don't quite get what you're saying. If the system becomes unresponsive

  1   2   >