All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Rik van Riel <riel@redhat.com>
Cc: Con Kolivas <kernel@kolivas.org>,
	ck kernel mailing list <ck@vds.kolivas.org>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8.1-ck4
Date: Wed, 25 Aug 2004 14:02:20 -0700	[thread overview]
Message-ID: <20040825210220.GK2793@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0408251656420.5145-100000@chimarrao.boston.redhat.com>

On Wed, 25 Aug 2004, William Lee Irwin III wrote:
>> This will be unmapped and clean; but that's not certain to be enough.
>> We must ask at what cost comes aggressive caching.

On Wed, Aug 25, 2004 at 04:56:53PM -0400, Rik van Riel wrote:
> Why isn't unmapped and clean enough ?

We don't know that it isn't; it merely remains to be proved that it is.


-- wli

  reply	other threads:[~2004-08-25 21:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-22 11:17 2.6.8.1-ck4 Con Kolivas
2004-08-22 18:15 ` 2.6.8.1-ck4 Hans Reiser
2004-08-22 21:37   ` 2.6.8.1-ck4 Con Kolivas
2004-08-23 17:04 ` 2.6.8.1-ck4 Joshua Schmidlkofer
2004-08-23 17:19   ` 2.6.8.1-ck4 Prakash K. Cheemplavam
2004-08-23 17:31     ` 2.6.8.1-ck4 Joshua Schmidlkofer
2004-08-23 21:48     ` 2.6.8.1-ck4 Con Kolivas
2004-08-23 23:34       ` 2.6.8.1-ck4 Con Kolivas
2004-08-24  9:28         ` 2.6.8.1-ck4 Prakash K. Cheemplavam
2004-08-24  9:43           ` 2.6.8.1-ck4 Con Kolivas
2004-08-24  9:54             ` 2.6.8.1-ck4 Prakash K. Cheemplavam
2004-08-25 20:22 ` 2.6.8.1-ck4 Rik van Riel
2004-08-25 20:50   ` 2.6.8.1-ck4 William Lee Irwin III
2004-08-25 20:56     ` 2.6.8.1-ck4 Rik van Riel
2004-08-25 21:02       ` William Lee Irwin III [this message]
2004-08-26  0:10   ` 2.6.8.1-ck4 Con Kolivas

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=20040825210220.GK2793@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=ck@vds.kolivas.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.