Re: Ingo Molnar and Con Kolivas 2.6 scheduler patches

From: Rob Landley (rob_at_landley.net)
Date: 08/14/03

  • Next message: John Newbie: "ide drives performance issues, maybe related with buffer cache." 
    To: George Anzinger <george@mvista.com>
Date:	Wed, 13 Aug 2003 20:24:36 -0400

    On Saturday 09 August 2003 16:52, George Anzinger wrote:
    > Ed Sweetman wrote:
    > > the problem is you want a process that works like it was run on a single
    > > tasking OS on an operating system that is built from the ground up to be
    > > a multi-user multi-tasking OS

    Considering the multi-tasking OS has 1000 times the CPU power, memory, and
    disk space as the single-tasking OS did when it debuted, yet still loses to
    it in some areas, isn't it at least worth looking at?

    > > and you want both to work perfectly at peak performance

    We're pondering various heuristics with which to to improve the situation and
    you say we're persuing perfection. From heuristics.

    Do you say these sort of things to the virtual memory people? (Since you
    can't do it perfectly, why bother to swap at all? The perfect being the
    enemy of the good, and all that.)

    > > and you want it to know when you want which to work at
    > > peak performance automatically.

    I know for a fact that automatic determination of interactivity is possible.
    In OS/2 you could speed up a compile by moving the mouse pointer over its
    window repeatedly to give it extra clock ticks. (So far we've managed to
    avoid anything quite so disgusting in Linux, but there exist OSes where it
    was done. Having the keyboard and mouse and display be local devices is
    actually the common case. It took X about ten years to finally start
    optimizing for the common case on the output side with MIT shared memory
    extensions and such...)

    The scheduler actually has a lot of information to work with. Ingo's patches
    strive to give it more information, and and Con's patches make much better
    use of that information. This is a good thing.

    > Well said :)

    Actually, I didn't really consider that list of straw man arguments to be
    worth commenting on the first time around. (I thought he was being
    sarcastic...)

    Rob
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: John Newbie: "ide drives performance issues, maybe related with buffer cache."

    Relevant Pages

    • Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
      ... value on ppc64. ... My system has 6GB of memory and I would 'load ... Without these patches, it was almost impossible ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.3-mm4-rcu_ll SMP memory leak ?
      ... > I'm running said kernel, and after 5 days I've noticed that all my ... > is there some way to see how much memory the kernel uses for its ... Is it vanilla 2.6.3-mm4 or it has some other patches in it? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Ingo Molnar and Con Kolivas 2.6 scheduler patches
      ... > you say we're persuing perfection. ... > Do you say these sort of things to the virtual memory people? ... > strive to give it more information, and and Con's patches make much better ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: VM patches in 2.6.4-rc1-mm2
      ... Mainline doesn't put enough pressure on slab with highmem systems. ... you don't do any mapped memory scaning at all ... The patches you are using do not address this. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • RE: [PATCHv5 3/3] vhost_net: a kernel-level virtio server
      ... I have collected your 3 patches in kernel side and 4 patches in queue side. ... structures can be moved around in memory at any time ... Userspace hypervisors are supported as well as kvm. ... In this version I only support raw socket as a backend, ...
      (Linux-Kernel)
    Loading