From: "Santosh Abraham" <santosha@india.hp.com>
To: "'Randolph Chung'" <randolph@tausq.org>
Cc: <parisc-linux@lists.parisc-linux.org>
Subject: RE: [parisc-linux] Fwd: Problems with raw interface.
Date: Thu, 25 Sep 2003 16:49:21 +0530 [thread overview]
Message-ID: <000801c38356$dea5cda0$e5624c0f@india.hp.com> (raw)
In-Reply-To: <20030925105005.GX16872@tausq.org>
hmm.. why is map_user_kiobuf () calling flush_dcache_page () then ?
should it not be calling flush_cache_{range,page} ?
map_user_kiobuf () called from the raw I/O path should ,in the
write case, be flushing user data out, so that its visible to
the kernel VA.
This is not being done in flush_dcache_page () when page->mapping is
NULL.
-----Original Message-----
From: Randolph Chung [mailto:randolph@tausq.org]
Sent: Thursday, September 25, 2003 4:20 PM
To: santosh.abraham@hp.com
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Fwd: Problems with raw interface.
> Also, does'nt __flush_dcache_page () need to have a for loop for "i_mmap"
> similar to the one for "i_mmap_shared" ?
>
no, this was discussed recently on this list.
see jejb's message:
http://lists.parisc-linux.org/pipermail/parisc-linux/2003-August/020791.html
and the corresponding thread for more info.
i thought flush_dcache_page is for making kernel mapping visible to
user, if you are trying to make user data visible to the kernel, you
should not be relying on flush_dcache_page.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
next prev parent reply other threads:[~2003-09-25 11:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 10:38 [parisc-linux] Fwd: Problems with raw interface Santosh Abraham
2003-09-25 10:50 ` Randolph Chung
2003-09-25 11:19 ` Santosh Abraham [this message]
2003-09-25 14:26 ` Matthew Wilcox
2003-09-26 1:08 ` David S. Miller
2003-09-26 11:24 ` Matthew Wilcox
2003-09-26 11:20 ` David S. Miller
2003-09-26 11:57 ` Stephen C. Tweedie
2003-09-26 11:48 ` David S. Miller
2003-09-26 12:20 ` Matthew Wilcox
2003-09-26 12:38 ` David S. Miller
2003-09-26 13:11 ` SANTOSH ABRAHAM
2003-09-26 12:56 ` David S. Miller
2003-09-26 13:29 ` Matthew Wilcox
2003-09-26 13:21 ` David S. Miller
2003-09-26 14:09 ` Matthew Wilcox
2003-09-26 14:04 ` David S. Miller
2003-09-26 14:30 ` Matthew Wilcox
2003-09-26 14:20 ` David S. Miller
2003-09-26 14:42 ` Stephen C. Tweedie
2003-09-26 14:26 ` Stephen C. Tweedie
2003-09-26 11:47 ` Santosh Abraham
2003-09-26 10:42 ` Santosh Abraham
2003-09-26 10:34 ` David S. Miller
2003-09-26 12:12 ` Santosh Abraham
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='000801c38356$dea5cda0$e5624c0f@india.hp.com' \
--to=santosha@india.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.org \
--cc=santosh.abraham@hp.com \
/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