Linux PARISC architecture development
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Grant Grundler <grantgrundler@gmail.com>,
	linux-parisc List <linux-parisc@vger.kernel.org>
Subject: Re: Happy New Year PARISC
Date: Tue, 03 Jan 2012 10:13:30 -0500	[thread overview]
Message-ID: <4F031B1A.4010908@bell.net> (raw)
In-Reply-To: <CADZpyiywh8SL42H9nO=9tMXgiyxL4SfmaX6PcZP5Kwme-Ozxsw@mail.gmail.com>

On 1/3/2012 6:50 AM, Carlos O'Donell wrote:
> On Mon, Jan 2, 2012 at 6:12 PM, John David Anglin<dave.anglin@bell.net>  wrote:
>> None of this worked.  Attached patch as it stands.  Comments and testing
>> appreciated.
> Could you clarify what you mean by "none of this worked?"
>

I tried eliminating the flushes that occur in kunmap_atomic on PA8800 
and PA8900
after the calls to clear_user_page and copy_user_page by defining 
clear_user_highpage
and copy_user_highpage.  I had thought the flushes weren't necessary.  
There's something
about this that I don't understand.  Why do we need to flush 
non-equivalent page mappings
that aren't used?

Also tried:
#define flush_cache_dup_mm(mm)        do { } while (0)

In both cases, init died causing a panic at boot.  Maybe there's 
something missing at
startup.

Most arch's have the above define for flush_cache_dup_mm.  Our define 
really hurts
fork performance.  The GCC testsuite takes almost twice as long to run 
on linux as hpux.
On the other hand, build times are fairly comparable.

Dave

-- 
John David Anglin    dave.anglin@bell.net


  reply	other threads:[~2012-01-03 15:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-01  0:02 Happy New Year PARISC John David Anglin
2012-01-02  6:23 ` Grant Grundler
2012-01-02 15:12   ` John David Anglin
2012-01-02 23:12     ` John David Anglin
2012-01-03 11:50       ` Carlos O'Donell
2012-01-03 15:13         ` John David Anglin [this message]
2012-01-03 15:32           ` James Bottomley
2012-01-03 15:32           ` James Bottomley
2012-01-03 16:26             ` John David Anglin
2012-01-03 16:42               ` John David Anglin
2012-01-03 16:42               ` James Bottomley
2012-01-03 18:39                 ` John David Anglin
2012-01-29 21:45                   ` Happy New Year PARISC (take 2) John David Anglin
     [not found]                     ` <CA+DQjFiTwKC76Hn-x-s2C9Nc_qkqrRFXv3ji22KGtgMzGOfx0Q@mail.gmail.com>
2012-01-30  1:06                       ` Thibaut VARENE
2012-02-28 15:28                     ` John David Anglin
2012-02-28 22:56                       ` Domenico Andreoli
2012-02-29  1:28                         ` John David Anglin
2012-03-01  0:48                         ` John David Anglin

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=4F031B1A.4010908@bell.net \
    --to=dave.anglin@bell.net \
    --cc=carlos@systemhalted.org \
    --cc=grantgrundler@gmail.com \
    --cc=linux-parisc@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