From: "Dmitry Adamushko" <dmitry.adamushko@gmail.com>
To: "Nick Piggin" <nickpiggin@yahoo.com.au>
Cc: "Russell King - ARM Linux" <linux@arm.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
"Naval Saini" <navalnovel@gmail.com>,
linux-arch@vger.kernel.org,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-kernel@vger.kernel.org, naval.saini@nxp.com,
"Ralf Baechle" <ralf@linux-mips.org>
Subject: Re: O_DIRECT patch for processors with VIPT cache for mainline kernel (specifically arm in our case)
Date: Thu, 20 Nov 2008 13:28:03 +0100 [thread overview]
Message-ID: <b647ffbd0811200428u2b41b108ifb02872563c871ab@mail.gmail.com> (raw)
In-Reply-To: <200811201759.01039.nickpiggin@yahoo.com.au>
2008/11/20 Nick Piggin <nickpiggin@yahoo.com.au>:
>
> [ ... ]
>
> - The page is sent to the block layer, which stores into the page. Some
> block devices like 'brd' will potentially store via the kernel linear map
> here, and they probably don't do enough cache flushing.
btw., if someone is curious, here is another case of what may happen
on VIPT systems when someone uses a "virtual" block device (like
'brd') as, heh, a swap :-)
http://www.linux-mips.org/archives/linux-mips/2008-11/msg00038.html
--
Best regards,
Dmitry Adamushko
next prev parent reply other threads:[~2008-11-20 12:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d8dd82df0811180606w503563ach8650ab07dcd0a35c@mail.gmail.com>
[not found] ` <200811191740.23638.nickpiggin@yahoo.com.au>
[not found] ` <20081119204315.GB17209@flint.arm.linux.org.uk>
2008-11-20 6:59 ` O_DIRECT patch for processors with VIPT cache for mainline kernel (specifically arm in our case) Nick Piggin
2008-11-20 9:19 ` Russell King - ARM Linux
2008-11-20 10:55 ` Naval Saini
2008-11-21 17:10 ` Catalin Marinas
2008-11-20 12:28 ` Dmitry Adamushko [this message]
2008-11-20 13:25 ` Nick Piggin
2008-11-20 13:55 ` Ralf Baechle
2008-11-20 15:27 ` Matthew Wilcox
2008-11-20 17:17 ` Ralf Baechle
2008-11-20 17:40 ` Matthew Wilcox
2008-11-20 19:30 ` Russell King - ARM Linux
2008-11-20 16:30 ` Russell King - ARM Linux
2008-11-20 13:59 ` Dmitry Adamushko
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=b647ffbd0811200428u2b41b108ifb02872563c871ab@mail.gmail.com \
--to=dmitry.adamushko@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=naval.saini@nxp.com \
--cc=navalnovel@gmail.com \
--cc=nickpiggin@yahoo.com.au \
--cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).