LKML Archive on
help / color / mirror / Atom feed
From: "Jaya Kumar" <>
To: "Paul Mundt" <>,
	"Jaya Kumar" <>,,,,
	"Andrew Morton" <>
Subject: Re: [PATCH/RFC 2.6.20 1/2] fbdev, mm: Deferred IO support
Date: Thu, 1 Mar 2007 19:02:34 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 3/1/07, Paul Mundt <> wrote:
> On Sun, Feb 25, 2007 at 06:13:12AM +0100, Jaya Kumar wrote:
> > This patch implements deferred IO support in fbdev. Deferred IO is a way to
> > delay and repurpose IO. This implementation is done using mm's page_mkwrite
> > and page_mkclean hooks in order to detect, delay and then rewrite IO. This
> > functionality is used by hecubafb.
> >
> Any updates on this? If there are no other concerns, it would be nice to
> at least get this in to -mm for testing if nothing else.

I think Andrew merged it into -mm.

> Jaya, can you roll the fsync() patch in to your defio patch? There's not
> much point in keeping them separate.

I forgot to add that. Sorry about that. Should I resubmit with it or
would you prefer to post it?


  parent reply	other threads:[~2007-03-02  0:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-25  5:13 [PATCH/RFC 2.6.20 1/2] fbdev, mm: Deferred IO support Jaya Kumar
2007-02-25  5:13 ` [PATCH/RFC 2.6.20 2/2] fbdev: Hecuba fb driver Jaya Kumar
2007-03-01 14:01 ` [PATCH/RFC 2.6.20 1/2] fbdev, mm: Deferred IO support Paul Mundt
2007-03-01 23:44   ` [Linux-fbdev-devel] " Antonino Daplas
2007-03-02  0:02   ` Jaya Kumar [this message]
2007-03-02  2:00     ` Paul Mundt

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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).