linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Rene Herman <rene.herman@gmail.com>
Cc: Mike Galbraith <efault@gmx.de>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	Andika Triwidada <andika@gmail.com>,
	Robert Deaton <false.hopes@gmail.com>,
	linux-kernel@vger.kernel.org, ck list <ck@vds.kolivas.org>,
	linux-mm@kvack.org, B.Steinbrink@gmx.de,
	Andrew Morton <akpm@osdl.org>
Subject: Re: updatedb
Date: Fri, 27 Jul 2007 15:32:10 +0200	[thread overview]
Message-ID: <46A9F3DA.2090203@imap.cc> (raw)
In-Reply-To: <46A9E4FC.80403@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1346 bytes --]

Rene Herman schrieb:
> On 07/27/2007 01:48 PM, Mike Galbraith wrote:
> 
>> I believe the users who say their apps really do get paged back in
>> though, so suspect that's not the case.
> 
> Stopping the bush-circumference beating, I do not. -ck (and gentoo) have 
> this massive Calimero thing going among their users where people are much 
> less interested in technology than in how the nasty big kernel meanies are 
> keeping them down (*).

I think the problem is elsewhere. Users don't say: "My apps get paged
back in." They say: "My system is more responsive". They really don't
care *why* the reaction to a mouse click that takes three seconds with
a mainline kernel is instantaneous with -ck. Nasty big kernel meanies,
OTOH, want to understand *why* a patch helps in order to decide whether
it is really a good idea to merge it. So you've got a bunch of patches
(aka -ck) which visibly improve the overall responsiveness of a desktop
system, but apparently no one can conclusively explain why or how they
achieve that, and therefore they cannot be merged into mainline.

I don't have a solution to that dilemma either.

-- 
Tilman Schmidt                    E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2007-07-27 13:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-25 15:30 howto get a patch merged (WAS: Re: -mm merge plans for 2.6.23) Kacper Wysocki
2007-07-25 16:01 ` Rene Herman
2007-07-25 17:15   ` Robert Deaton
2007-07-26  3:59     ` updatedb Rene Herman
2007-07-26  6:23       ` updatedb Andika Triwidada
2007-07-26  7:49         ` updatedb Rene Herman
2007-07-26  9:37           ` updatedb Andika Triwidada
2007-07-27  0:46         ` updatedb Jesper Juhl
2007-07-27  6:00           ` updatedb Rene Herman
2007-07-27  7:54             ` updatedb Mike Galbraith
2007-07-27  8:28               ` updatedb Rene Herman
2007-07-27  9:26                 ` updatedb Mike Galbraith
2007-07-27 11:09                   ` updatedb Rene Herman
2007-07-27 11:48                     ` updatedb Mike Galbraith
2007-07-27 12:28                       ` updatedb Rene Herman
2007-07-27 13:32                         ` Tilman Schmidt [this message]
2007-07-26  6:39       ` updatedb Bongani Hlope
2007-07-26  6:56         ` updatedb Rene Herman
2007-07-26  7:08           ` updatedb Bongani Hlope
2007-07-26  8:01             ` updatedb Rene Herman
2007-07-26 21:25               ` updatedb Bongani Hlope
2007-07-26  9:58           ` updatedb Björn Steinbrink
2007-07-26 10:23             ` updatedb Björn Steinbrink
2007-07-26 11:00             ` updatedb Rene Herman
2007-07-26 13:54     ` Re: howto get a patch merged (WAS: Re: -mm merge plans for 2.6.23) Jos Poortvliet
2007-07-25 16:07 ` Ingo Molnar
2007-07-25 16:40   ` [ck] " Michael Chang

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=46A9F3DA.2090203@imap.cc \
    --to=tilman@imap.cc \
    --cc=B.Steinbrink@gmx.de \
    --cc=akpm@osdl.org \
    --cc=andika@gmail.com \
    --cc=ck@vds.kolivas.org \
    --cc=efault@gmx.de \
    --cc=false.hopes@gmail.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rene.herman@gmail.com \
    /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