[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1168586145.26496.35.camel@twins>
Date: Fri, 12 Jan 2007 08:15:45 +0100
From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
To: Jaya Kumar <jayakumar.lkml@...il.com>
Cc: Andrew Morton <akpm@...l.org>,
linux-fbdev-devel@...ts.sourceforge.net,
linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH/RFC 2.6.20-rc4 1/1] fbdev,mm: hecuba/E-Ink fbdev driver
On Thu, 2007-01-11 at 19:22 -0500, Jaya Kumar wrote:
> Agreed. Though I may be misunderstanding what you mean by first-touch.
> Currently, I do a schedule_delayed_work and leave 1s between when the
> page_mkwrite callback indicating the first touch is received and when
> the deferred IO is processed to actually deliver the data to the
> display. I picked 1s because it rounds up the display latency. I
> imagine increasing the delay further may make it miss some desirable
> display activity. For example, a slider indicating progress of music
> may be slower than optimal. Perhaps I should make the delay a module
> parameter and leave the choice to the user?
How about implementing the sync_page() aop? Then you could force the
flush using msync(MS_SYNC).
Hmm... that might require more surgery but the idea would work I think.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists