public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
	"Robert Love" <rml@tech9.net>,
	"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Balanced Multi Queue Scheduler ...
Date: Sun, 30 Dec 2001 00:38:12 +0100	[thread overview]
Message-ID: <200112292338.AAA29985@webserver.ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0112291424560.1580-100000@blue1.dev.mcafeelabs.com>

> On Sat, 29 Dec 2001, Dieter [iso-8859-15] Nützel wrote:             
>                                                                     
> The new patch need ver >= 2.5.2-pre3 because Linus merged the Time  
Slice                                                                 
> Split Scheduler and making it to apply to 2.4.x could be a pain in  
the b*tt.                                                             
> Yes, as i expected numbers on big SMP are very good but still i     
don't                                                                 
> think that this can help you with your problem.                     
                                                                      
Just a short note on that:                                            
                                                                      
Before the scheduler stuff really got rolling there was a pretty      
distinct discussion why L didn't quite get involved in the thread. I  
may remind you that he thought it to be not a _that_ interesting stuff
and I well remember he said something about the smallness and the low 
possibility that it gets broken by (well-thought-out) patches. This   
leads me to believe he has no major issues with enhancements to 2.4   
scheduler.                                                            
Well, me neither :-)                                                  
In fact we should keep in mind that 2.5 is a _development_ kernel and 
a next stable branch is out-of-sight at this time. So it would be     
quite reasonable to do a "backport" to 2.4 of the scheduler, because  
SMP systems do get more in size and number today and the near future. 
And we should not expect the not-LKML world to use _development_      
kernels on their cool-nu-SMP-box (tm), because this can only be bad   
for ongoing comparisons with other OSs. Well, you know what I mean.   
In fact I can see two major steps to take for marcelo's maintenance   
(besides the bugfixes of course):                                     
1) the SMP-scheduling (its all yours, Davide :-)                      
2) the HIGHMEM problems (a warm welcome to Andrea :-)                 
We cannot deny the fact that people expect the scalability of the     
system, and just to give you a small hint, I personally already       
stopped buying UP machines. There is no real big difference in prices 
between UP and 2-SMP these days, and RAM is unbelievably cheap in this
decade - and it makes your seti-statistics fly ;-)                    
So these issues will be very much in the mainstream of all users. No  
way to deny this.                                                     
I have no fear: this is a reachable goal, let's just take it.         
                                                                      
Regards,                                                              
Stephan                                                               
                                                                      
PS: Yes, Alan, I read your mail about the 32GB box and DMA and stuff, 
but nevertheless we should keep up with the market-ongoings (damn     
cheap 1GB modules).                                                   
                                                                      
                                                                      

  parent reply	other threads:[~2001-12-29 23:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-29  5:16 [PATCH] Balanced Multi Queue Scheduler Dieter Nützel
2001-12-29 22:29 ` Davide Libenzi
2001-12-29 22:49   ` Andrew Morton
2001-12-29 23:39     ` Davide Libenzi
2001-12-29 23:38   ` Stephan von Krawczynski [this message]
2001-12-30  0:02     ` Davide Libenzi
2001-12-30  2:32     ` Alan Cox
2001-12-30  3:11       ` Dieter Nützel
2001-12-30 19:47     ` Timothy Covell
2001-12-30 20:16       ` Davide Libenzi
2001-12-30 23:20         ` Stephan von Krawczynski
2001-12-30 23:46           ` Davide Libenzi
2001-12-31 16:37             ` Stephan von Krawczynski
2001-12-31 17:26               ` Davide Libenzi
2001-12-30 20:47       ` J Sloan
2001-12-30 20:53         ` Davide Libenzi
2001-12-30 21:12         ` Alan Cox
2001-12-30 23:16       ` Stephan von Krawczynski
2002-01-14  1:33       ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2001-12-29  3:53 Davide Libenzi

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=200112292338.AAA29985@webserver.ithnet.com \
    --to=skraw@ithnet.com \
    --cc=Dieter.Nuetzel@hamburg.de \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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