From: "Jaya Kumar" <jayakumar.lkml@gmail.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Stefani Seibold <stefani@seibold.net>,
Peter Zijlstra <peterz@infradead.org>,
linux-mm@kvack.org
Subject: Re: vm_ops.page_mkwrite() fails with vmalloc on 2.6.23
Date: Mon, 22 Oct 2007 13:03:20 -0400 [thread overview]
Message-ID: <45a44e480710221003u4b6d9e84n98599c97b9dab95@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710221719420.13779@blonde.wat.veritas.com>
On 10/22/07, Hugh Dickins <hugh@veritas.com> wrote:
>
> Interesting. You need to ask Jaya (CC'ed) since he's the one
> who put that code into fb_defio.c, exported page_mkclean, and
> should have tested it.
Thanks Hugh.
Yes, hecubafb uses fb_defio (which is infrastructure code) which uses
mkwrite/mkclean. This was tested and it worked great on x86 with
2.6.21 when I posted the patches.
I will be trying in the next few weeks to finish up a driver for the
current E-Ink Vizplex+controller working on arm with 2.6.22. So since
page_mkclean has changed, I will try to work on a update for fb_defio
at that time.
>
> >
> > I am not sure if the is a feature of the new rmap code or a bug.
>
> page_mkclean was written in the belief that it was being used on
> pagecache pages. I'm not sure how deeply engrained that belief is.
>
> If it can easily and safely be used on something else, that may be
> nice: though there's a danger we'll keep breaking and re-breaking
> it if there's only one driver using it in an unusual way. CC'ed
> Peter since he's the one who most needs to be aware of this.
Yes, right now, only hecubafb uses deferred IO and thus page_mkclean.
But I believe that usage will increase. I hope together we can get it
fixed up and keep it working long term. I think deferred IO gives
linux a nice advantage when interfacing with high latency displays (of
which one will increasingly see more of).
Thanks,
jaya
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-10-22 17:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-22 14:45 vm_ops.page_mkwrite() fails with vmalloc on 2.6.23 Stefani Seibold
2007-10-22 16:37 ` Hugh Dickins
2007-10-22 17:03 ` Jaya Kumar [this message]
2007-10-22 17:17 ` Peter Zijlstra
2007-10-22 17:20 ` Peter Zijlstra
[not found] <1193064057.16541.1.camel@matrix>
2007-10-29 7:40 ` Andrew Morton
2007-10-29 8:17 ` Jaya Kumar
2007-10-29 10:11 ` Peter Zijlstra
2007-10-29 12:35 ` Peter Zijlstra
2007-10-29 14:28 ` Nick Piggin
2007-10-29 17:01 ` Peter Zijlstra
2007-10-29 17:51 ` Jaya Kumar
2007-10-29 18:17 ` Peter Zijlstra
2007-10-29 22:16 ` Peter Zijlstra
2007-10-30 1:22 ` Jaya Kumar
2007-10-30 9:56 ` Peter Zijlstra
2007-10-30 10:49 ` Stefani Seibold
2007-10-30 12:39 ` Hugh Dickins
2007-10-30 13:12 ` Peter Zijlstra
2007-10-30 13:16 ` Jaya Kumar
2007-10-30 13:25 ` Peter Zijlstra
2007-10-30 15:47 ` Hugh Dickins
2007-10-30 15:51 ` Peter Zijlstra
2007-11-01 8:02 ` Jaya Kumar
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=45a44e480710221003u4b6d9e84n98599c97b9dab95@mail.gmail.com \
--to=jayakumar.lkml@gmail.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=stefani@seibold.net \
/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).