linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@us.ibm.com>
To: suparna@in.ibm.com
Cc: Alex Tomas <alex@clusterfs.com>,
	sct@redhat.com, akpm@osdl.org, linux-fsdevel@vger.kernel.org
Subject: Re: Delayed alloc for ordered-mode
Date: Sun, 13 Mar 2005 11:32:24 -0800	[thread overview]
Message-ID: <42349548.2030209@us.ibm.com> (raw)
In-Reply-To: <20050313144117.GA4471@in.ibm.com>

I think adding support to JBD to deal with "bio"s  would be
a valuable generic extention. Anyway its dealing with "bh"s
now.

Thanks,
Badari

Suparna Bhattacharya wrote:

> What would be really nice is if we could do this in a way that
> enables reuse of generic paths even for ordered mode. One thought
> that comes to mind is journal commit waiting for writeback to 
> complete on the data pages which need to be flushed to disk before 
> meta-data can be committed, much like we do for O_SYNC. 
> 
> I realise that JBD is intended to work at a level of abstraction
> where it has no awareness of filesystems - hence the correspondence
> with buffer heads all through. So would the above be a complete
> no-no ?
> 
> Regards
> Suparna
> 
> On Fri, Mar 04, 2005 at 06:02:35PM +0300, Alex Tomas wrote:
> 
>>On 03 Mar 2005 17:12:14 -0800
>>Badari Pulavarty <pbadari@us.ibm.com> wrote:
>>
>>
>>>One more thing, we need to keep in mind is - we need to make sure
>>>that "ordered" mode also improved - since all our testcode 
>>>focuses on "writeback" mode and the default mode is "ordered" :(
>>>
>>
>>I've just cooked the patch to implement ordered mode for delayed
>>allocation path. please take it:
>>
>>ftp://ftp.clusterfs.com/pub/people/alex/2.6.11/ext3-delalloc-ordered-2.6.11-0.1.patch
>>
>>Stephen, Andrew could you review it, please?
>>
>>thanks, Alex


      reply	other threads:[~2005-03-13 19:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-03  8:33 Reviewing ext3 improvement patches (delalloc, mballoc, extents) Suparna Bhattacharya
2005-03-03  9:40 ` Andreas Dilger
2005-03-03 22:10   ` Theodore Ts'o
2005-03-03 22:30     ` Alex Tomas
2005-03-04 11:13   ` Suparna Bhattacharya
2005-03-04 12:29     ` Alex Tomas
2005-03-04 18:25       ` [Ext2-devel] " Andreas Dilger
2005-03-04  1:12 ` [Ext2-devel] " Badari Pulavarty
2005-03-04  1:46   ` Mingming Cao
2005-03-04  3:26     ` Suparna Bhattacharya
2005-03-14  8:36     ` Werner Almesberger
2005-03-14  9:04       ` Suparna Bhattacharya
2005-03-14 15:02         ` Werner Almesberger
2005-03-14 15:43           ` Alex Tomas
2005-03-14 16:37             ` [Ext2-devel] " Werner Almesberger
2005-03-14 17:13               ` Alex Tomas
2005-03-15  0:28                 ` Werner Almesberger
2005-03-14 22:23               ` Bryan Henderson
2005-03-15  0:42                 ` Werner Almesberger
2005-03-15 21:59                   ` Bryan Henderson
2005-03-04 11:30   ` [Ext2-devel] " Alex Tomas
2005-03-04 15:02   ` Alex Tomas
2005-03-13 14:41     ` Delayed alloc for ordered-mode Suparna Bhattacharya
2005-03-13 19:32       ` Badari Pulavarty [this message]

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=42349548.2030209@us.ibm.com \
    --to=pbadari@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=alex@clusterfs.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=suparna@in.ibm.com \
    /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 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).