All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Jaya Kumar <jayakumar.lkml@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-fbdev-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH/RFC 2.6.20-rc4 1/1] fbdev,mm: hecuba/E-Ink fbdev driver
Date: Fri, 12 Jan 2007 08:15:45 +0100	[thread overview]
Message-ID: <1168586145.26496.35.camel@twins> (raw)
In-Reply-To: <45a44e480701111622i32fffddcn3b4270d539620743@mail.gmail.com>

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.

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Jaya Kumar <jayakumar.lkml@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-fbdev-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH/RFC 2.6.20-rc4 1/1] fbdev,mm: hecuba/E-Ink fbdev driver
Date: Fri, 12 Jan 2007 08:15:45 +0100	[thread overview]
Message-ID: <1168586145.26496.35.camel@twins> (raw)
In-Reply-To: <45a44e480701111622i32fffddcn3b4270d539620743@mail.gmail.com>

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, 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>

  parent reply	other threads:[~2007-01-12  7:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-11 14:24 [PATCH/RFC 2.6.20-rc4 1/1] fbdev, mm: hecuba/E-Ink fbdev driver Jaya Kumar
2007-01-11 14:24 ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev,mm: " Jaya Kumar
2007-01-11 14:24 ` Jaya Kumar
2007-01-11 21:37 ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev, mm: " Andrew Morton
2007-01-11 21:37   ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev,mm: " Andrew Morton
2007-01-11 21:37   ` Andrew Morton
2007-01-12  0:22   ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev, mm: " Jaya Kumar
2007-01-12  0:22     ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev,mm: " Jaya Kumar
2007-01-12  0:22     ` Jaya Kumar
2007-01-12  0:36     ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev, mm: " Andrew Morton
2007-01-12  0:36       ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev,mm: " Andrew Morton
2007-01-12  0:36       ` Andrew Morton
2007-01-12  0:47     ` Nick Piggin
2007-01-12  0:47       ` Nick Piggin
2007-02-17  9:47       ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev, mm: " Jaya Kumar
2007-02-17  9:47         ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev,mm: " Jaya Kumar
2007-02-17  9:47         ` Jaya Kumar
2007-01-12  7:15     ` Peter Zijlstra [this message]
2007-01-12  7:15       ` Peter Zijlstra
2007-01-12  7:25       ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev, mm: " Andrew Morton
2007-01-12  7:25         ` [PATCH/RFC 2.6.20-rc4 1/1] fbdev,mm: " Andrew Morton
2007-01-12  7:25         ` Andrew Morton

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=1168586145.26496.35.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@osdl.org \
    --cc=jayakumar.lkml@gmail.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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.