All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Loginov <isloginov@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Jens Axboe <jens.axboe@oracle.com>, linux-arch@vger.kernel.org
Subject: Re: problems in commit 2d4dc890b5c8 (block: add helpers to run flush_dcache_page() against a bio and a request's pages)
Date: Thu, 10 Dec 2009 03:06:38 +0300	[thread overview]
Message-ID: <20091210030638.db4cfd8a.isloginov@gmail.com> (raw)
In-Reply-To: <1260402471.14369.60.camel@mulgrave.site>

On Wed, 09 Dec 2009 17:47:51 -0600
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:

> Which architecture is this? ... because if it's missing a necessary
> definition for flush_kernel_dcache_page() it's very easy to add it ...

This is a MIPS. Why? The call flush_dcache_page() on MIPS is lazy enought.
And it do exactly what i need to fix the problem.

> > But. I could do that rq_flush_dcache_pages will call flush_kernel_dcache_page
> > for architectures where ARCH_HAS_FLUSH_KERNEL_DCACHE_PAGE was defined.
> 
> The point I'm trying to make is that flush_dcache_page() does a lot of
> unnecessary flushing.  Where you are in the system with the READ call,
> you know the user aliases are clean (because users aren't allowed to
> touch pages submitted for write), so you only (for efficiency) need to
> flush the dirty kernel alias.

I understand that in your case(parisc) solution with flushdcache_page()
is very voracious. But I don't think that we should change something
somewhere else except parisc. Or we should write to Ralf Baechle and
other maintainers and discuss all with them. Don't think?

-- 
Ilya Loginov <isloginov@gmail.com>

  reply	other threads:[~2009-12-10  0:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 22:39 problems in commit 2d4dc890b5c8 (block: add helpers to run flush_dcache_page() against a bio and a request's pages) James Bottomley
2009-12-09 22:45 ` Russell King
2009-12-09 22:56   ` James Bottomley
2009-12-09 23:03 ` Ilya Loginov
2009-12-09 23:11   ` James Bottomley
2009-12-09 23:36     ` Ilya Loginov
2009-12-09 23:47       ` James Bottomley
2009-12-10  0:06         ` Ilya Loginov [this message]
2009-12-10  0:19           ` James Bottomley
2009-12-10  4:40             ` Ilya Loginov
2009-12-10 17:07               ` James Bottomley
2009-12-10 17:48                 ` Russell King
2009-12-10 17:59                   ` James Bottomley
2009-12-10 18:06                     ` Russell King
2009-12-10 18:20                       ` James Bottomley
2009-12-10 19:05                         ` Russell King
2009-12-10 20:29                           ` James Bottomley
2009-12-10 20:39                             ` Russell King
2009-12-10 19:42                         ` Ilya Loginov
2009-12-10 19:43                           ` Russell King
2009-12-10 19:48                             ` Ilya Loginov
2009-12-10 19:46                 ` Ilya Loginov
2009-12-10 20:28                   ` James Bottomley
2009-12-10 20:41                     ` Ilya Loginov
2009-12-10 20:48                     ` Ilya Loginov
2009-12-10 20:59                       ` James Bottomley
2009-12-10 21:27                         ` Ilya Loginov
2009-12-10 21:43                           ` Ilya Loginov
2009-12-10 22:00                           ` James Bottomley
2009-12-10 22:03                             ` David Miller
2009-12-10 22:33                             ` Ilya Loginov

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=20091210030638.db4cfd8a.isloginov@gmail.com \
    --to=isloginov@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-arch@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 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.