From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Jambor Subject: Address space operations questions Date: Wed, 30 Mar 2005 00:30:55 +0200 Message-ID: <8e70aacf05032914306a827923@mail.gmail.com> References: <8e70aacf05032616151c958eed@mail.gmail.com> Reply-To: Martin Jambor Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from wproxy.gmail.com ([64.233.184.204]:43469 "EHLO wproxy.gmail.com") by vger.kernel.org with ESMTP id S261546AbVC2Waz (ORCPT ); Tue, 29 Mar 2005 17:30:55 -0500 Received: by wproxy.gmail.com with SMTP id 68so778196wri for ; Tue, 29 Mar 2005 14:30:55 -0800 (PST) To: linux-fsdevel@vger.kernel.org In-Reply-To: <8e70aacf05032616151c958eed@mail.gmail.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hi, I have problems understanding the purpose of different entries of struc address_space_operations in 2.6 kernels: 1. What is bmap for and what is it supposed to do? 2. What is the difference between sync_page and write_page? 3. What exactly (fs independent) is the relation in between write_page, prepare_write and commit_write? Does prepare make sure a page can be written (like allocating space), commit mark it dirty a write write it sometime later on? Thak you very much for any insight, Martin P.S.: I have dedicated a lot of time searching for any documentation, tried IRC forums and even bought a book without getting a truly good answer to the above questions. Oh yeah, I read a lot of the source even though not all of it yet :-) On the other hand, if you find this question inappropriate for this mailing list (too basic, perhaps), please let me know.