From: Mark Williamson Subject: Trying to cause a writepage from commit_write? Date: Wed, 4 Oct 2006 15:34:04 +0100 Message-ID: <200610041534.04743.mark.williamson@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from ppsw-0.csi.cam.ac.uk ([131.111.8.130]:14302 "EHLO ppsw-0.csi.cam.ac.uk") by vger.kernel.org with ESMTP id S1161141AbWJDOeD (ORCPT ); Wed, 4 Oct 2006 10:34:03 -0400 Received: from maw48.kings.cam.ac.uk ([128.232.241.233]:41698 helo=maw48) by ppsw-0.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.150]:25) with esmtpsa (PLAIN:maw48) (TLSv1:DHE-RSA-AES256-SHA:256) id 1GV7oX-0004iT-0Q (Exim 4.63) for linux-fsdevel@vger.kernel.org (return-path ); Wed, 04 Oct 2006 15:33:37 +0100 To: linux-fsdevel@vger.kernel.org Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi there, I'm writing a custom filesystem that does not use a block device as it's backing store. I think it should be possible to arrange for a writepage to be called at some point after a commit_write - for instance by just dirtying the page and waiting for it to be flushed. I've tried various methods for dirtying the page, but my writepage() method never seems to get called. I can't see anything obvious that I'm missing, but most other filesystems end up calling into the block layer at some point, so they don't correspond very well to what I'm trying to do. Any suggestions or pointers would be greatly appreciated. Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel!