From: Bill Davidsen <davidsen@tmr.com>
To: Robert Love <rml@tech9.net>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
bcrl@redhat.com, akpm@digeo.com, mbligh@aracnet.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.68-mm2
Date: Sat, 26 Apr 2003 06:34:07 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1030426062917.20200A-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <1051295252.9767.143.camel@localhost>
On 25 Apr 2003, Robert Love wrote:
> On Fri, 2003-04-25 at 14:20, Randy.Dunlap wrote:
> >
> > | The point is that even if bash is fixed it's desirable to address the
> > | issue in the kernel, other applications may well misbehave as well.
> >
> > So when would this ever end?
>
> Exactly what I was thinking.
>
> The kernel cannot be expected to cater to applications or make
> concessions (read: hacks) for certain behavior. If we offer a cleaner,
> improved interface which offers the performance improvement, we are
> done. Applications need to start using it.
>
> Of course, I am not arguing against optimizing the old interfaces or
> anything of that nature. I just believe we should not introduce hacks
> for application behavior. It is their job to do the right thing.
I don't care much if the kernel does something to make an application run
better, that's an application problem. But if an application can do
something which hurts the performance of the system as a whole, then the
kernel should protect itself and the rest of the system.
So I'm not advocating that the kernel cater to bash, just that doing
legitimate things with bash not have a disproportionate impact on the rest
of the system.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-04-26 10:34 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 8:20 2.5.68-mm2 Andrew Morton
2003-04-23 9:59 ` 2.5.68-mm2 William Lee Irwin III
2003-04-23 16:50 ` 2.5.68-mm2 Robert Love
2003-04-23 16:57 ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 17:11 ` 2.5.68-mm2 Robert Love
2003-04-24 9:14 ` 2.5.68-mm2 William Lee Irwin III
2003-04-23 12:08 ` 2.5.68-mm2 Ed Tomlinson
2003-04-23 12:37 ` 2.5.68-mm2 William Lee Irwin III
2003-04-23 14:25 ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 14:51 ` 2.5.68-mm2 Martin J. Bligh
2003-04-23 15:14 ` 2.5.68-mm2 Alex Tomas
2003-04-23 21:46 ` 2.5.68-mm2 Andrew Morton
2003-04-23 21:47 ` 2.5.68-mm2 Martin J. Bligh
2003-04-24 3:39 ` 2.5.68-mm2 Benjamin LaHaise
2003-04-24 21:13 ` 2.5.68-mm2 Martin J. Bligh
2003-04-24 23:13 ` objrmap (was 2.5.68-mm2) Martin J. Bligh
2003-04-24 3:36 ` 2.5.68-mm2 Benjamin LaHaise
2003-04-24 20:24 ` 2.5.68-mm2 Bill Davidsen
2003-04-24 20:33 ` 2.5.68-mm2 Benjamin LaHaise
2003-04-25 17:56 ` 2.5.68-mm2 Bill Davidsen
2003-04-25 18:20 ` 2.5.68-mm2 Randy.Dunlap
2003-04-25 18:27 ` 2.5.68-mm2 Robert Love
2003-04-25 18:49 ` 2.5.68-mm2 Martin J. Bligh
2003-04-26 10:34 ` Bill Davidsen [this message]
2003-04-26 15:34 ` 2.5.68-mm2 Martin J. Bligh
2003-05-01 6:19 ` [BUG] 2.5.68-mm2 and list.h Alexander Hoogerhuis
2003-05-01 6:31 ` Andrew Morton
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=Pine.LNX.3.96.1030426062917.20200A-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=akpm@digeo.com \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mbligh@aracnet.com \
--cc=rddunlap@osdl.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