public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Andrea Arcangeli <andrea@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19pre7aa1
Date: Sat, 20 Apr 2002 12:37:51 -0700	[thread overview]
Message-ID: <3CC1C38F.37D1F8C2@zip.com.au> (raw)
In-Reply-To: <20020420194213.K1291@dualathlon.random>

Andrea Arcangeli wrote:
> 
> ...
> Only in 2.4.19pre6aa1: 00_prepare-write-fixes-2
> Only in 2.4.19pre7aa1: 00_prepare-write-fixes-3
> 
>         Add a missing flush_dcache_page() to the prepare write corruption
>         fixes. Noticed by Andrew Morton.
> 

Why do we perform those "flushes"[1] at all?  The memsets should
never occur when the page is mapped into any process tables.

I seem to be missing something here.


[1] Can we please not that term?  A "flush" is something which you
    do to a "dunny" after taking a "crap". [2]

    Caches are either "written back" or are "invalidated".  Nothing
    else.

    This is not just semantics.  This stuff is hard.  90% of kernel
    developers are on x86, and 90% of those do not understand the
    nuances of all this.  The careful choice and use of terminology
    will aid other platforms.

[2] And a "sync" is something which you wash your hands in after the
    "flush".

    Dirty disk data is either "written out" or is "waited upon".  The
    kernel has real performance bugs due to this confusion.

-

  reply	other threads:[~2002-04-20 19:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20 17:42 2.4.19pre7aa1 Andrea Arcangeli
2002-04-20 19:37 ` Andrew Morton [this message]
2002-04-20 21:38   ` 2.4.19pre7aa1 Andrea Arcangeli
2002-04-20 22:12   ` 2.4.19pre7aa1 Ruth Ivimey-Cook
2002-04-20 22:56     ` 2.4.19pre7aa1 J. Dow
2002-04-21  0:09       ` 2.4.19pre7aa1 Anton Blanchard
2002-04-20 23:57     ` 2.4.19pre7aa1 Anton Blanchard

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=3CC1C38F.37D1F8C2@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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