From: Nitin Gupta <ngupta@vflare.org>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>,
David Miller <davem@davemloft.net>, Nick Piggin <npiggin@suse.de>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] [ARM] force dcache flush if dcache_dirty bit set
Date: Mon, 12 Oct 2009 22:42:22 +0530 [thread overview]
Message-ID: <4AD36376.60007@vflare.org> (raw)
In-Reply-To: <20091012170312.GB9453@flint.arm.linux.org.uk>
On 10/12/2009 10:33 PM, Russell King wrote:
> On Mon, Oct 12, 2009 at 05:09:53PM +0100, Hugh Dickins wrote:
>> Sorry to muddy the waters on this, if you and Dave are sure that
>> you have the right fix, down in your architectures, and that fix
>> isn't going to hurt your performance significantly.
>
> If I look at the issue from this point of view:
>
> - we are using PG_arch_1 to delay cache handling for the page
>
> - if PG_arch_1 is set on a page, we set it explicitly because we
> didn't do some flushing between the allocation of the page and
> mapping it into userspace
>
> - if a page with PG_arch_1 set ever gets to userspace, this can
> only be because we did the lazy flushing thing
>
> I don't see that there should have been any bearing on whether a page
> has a mapping or not when we get to update_mmu_cache. The issue here
> is that > if PG_arch_1 is set on a page, then we didn't flush it at
> the time when we believed it was appropriate to do so. <
>
Presented so clearly by Russell and this is exactly what I meant, though
the example just focused on some particular swap case which I happen to
stumble upon while working on something similar.
Thanks,
Nitin
WARNING: multiple messages have this Message-ID (diff)
From: ngupta@vflare.org (Nitin Gupta)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [ARM] force dcache flush if dcache_dirty bit set
Date: Mon, 12 Oct 2009 22:42:22 +0530 [thread overview]
Message-ID: <4AD36376.60007@vflare.org> (raw)
In-Reply-To: <20091012170312.GB9453@flint.arm.linux.org.uk>
On 10/12/2009 10:33 PM, Russell King wrote:
> On Mon, Oct 12, 2009 at 05:09:53PM +0100, Hugh Dickins wrote:
>> Sorry to muddy the waters on this, if you and Dave are sure that
>> you have the right fix, down in your architectures, and that fix
>> isn't going to hurt your performance significantly.
>
> If I look at the issue from this point of view:
>
> - we are using PG_arch_1 to delay cache handling for the page
>
> - if PG_arch_1 is set on a page, we set it explicitly because we
> didn't do some flushing between the allocation of the page and
> mapping it into userspace
>
> - if a page with PG_arch_1 set ever gets to userspace, this can
> only be because we did the lazy flushing thing
>
> I don't see that there should have been any bearing on whether a page
> has a mapping or not when we get to update_mmu_cache. The issue here
> is that > if PG_arch_1 is set on a page, then we didn't flush it at
> the time when we believed it was appropriate to do so. <
>
Presented so clearly by Russell and this is exactly what I meant, though
the example just focused on some particular swap case which I happen to
stumble upon while working on something similar.
Thanks,
Nitin
next prev parent reply other threads:[~2009-10-12 17:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 8:50 [PATCH] [ARM] force dcache flush if dcache_dirty bit set Nitin Gupta
2009-10-12 8:50 ` Nitin Gupta
2009-10-12 9:07 ` Russell King - ARM Linux
2009-10-12 9:07 ` Russell King - ARM Linux
2009-10-12 9:37 ` David Miller
2009-10-12 9:37 ` David Miller
2009-10-12 10:00 ` Russell King - ARM Linux
2009-10-12 10:00 ` Russell King - ARM Linux
2009-10-12 10:16 ` David Miller
2009-10-12 10:16 ` David Miller
2009-10-12 16:09 ` Hugh Dickins
2009-10-12 16:09 ` Hugh Dickins
2009-10-12 16:09 ` Hugh Dickins
2009-10-12 17:03 ` Russell King
2009-10-12 17:03 ` Russell King
2009-10-12 17:12 ` Nitin Gupta
2009-10-12 17:12 ` Nitin Gupta [this message]
2009-10-12 17:12 ` Nitin Gupta
2009-10-12 18:06 ` Hugh Dickins
2009-10-12 18:06 ` Hugh Dickins
2009-10-12 18:06 ` Hugh Dickins
2009-10-15 21:48 ` Kyle McMartin
2009-10-15 21:48 ` Kyle McMartin
2009-10-15 21:48 ` Kyle McMartin
2009-10-13 2:07 ` Paul Mundt
2009-10-13 2:07 ` Paul Mundt
2009-10-14 17:10 ` Catalin Marinas
2009-10-14 17:10 ` Catalin Marinas
2009-10-14 17:10 ` Catalin Marinas
2009-10-15 11:59 ` Catalin Marinas
2009-10-15 11:59 ` Catalin Marinas
2009-10-15 11:59 ` Catalin Marinas
2009-10-13 2:07 ` Paul Mundt
2009-10-12 10:28 ` Nitin Gupta
2009-10-12 10:28 ` Nitin Gupta
2009-10-12 11:08 ` Russell King - ARM Linux
2009-10-12 11:08 ` Russell King - ARM Linux
2009-10-12 11:16 ` Nitin Gupta
2009-10-12 11:16 ` Nitin Gupta
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=4AD36376.60007@vflare.org \
--to=ngupta@vflare.org \
--cc=davem@davemloft.net \
--cc=hugh.dickins@tiscali.co.uk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
/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.