From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Mingming Cao <cmm@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>,
"Stephen C. Tweedie" <sct@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
ext2-devel <ext2-devel@lists.sourceforge.net>,
linux-fsdevel@vger.kernel.org
Subject: Re: [Ext2-devel] [RFC] Adding multiple block allocation
Date: Sat, 30 Apr 2005 22:33:31 +0530 [thread overview]
Message-ID: <20050430170331.GE3941@in.ibm.com> (raw)
In-Reply-To: <1114821866.7635.7.camel@localhost.localdomain>
On Fri, Apr 29, 2005 at 05:44:26PM -0700, Mingming Cao wrote:
> Oops, sorry about the empty message ...
>
> > -static int ext3_writepages_get_block(struct inode *inode, sector_t iblock,
> > - struct buffer_head *bh, int create)
> > +static int ext3_writepages_get_blocks(struct inode *inode, sector_t iblock,
> > + unsigned long max_blocks, struct buffer_head *bh, int create)
> > {
> > - return ext3_direct_io_get_blocks(inode, iblock, 1, bh, create);
> > + return ext3_direct_io_get_blocks(inode, iblock, max_blocks, bh, create);
> > }
> >
>
> I have a question here, ext3_direct_io_get_blocks use DIO_CREDITS
> (EXT3_RESERVE_TRANS_BLOCKS + 32 = ) to reserve the space for
> journalling, but it seems based on assumption of one data block update
> once a time. Is it sufficent to re-use that routine for multiple block
> allocation here? Don't we need something like
> ext3_writepage_trans_blocks() here?
Quite likely - with your patch, as get_blocks actually allocates
multiple blocks at a time, the min credits estimate would
change for ext3_direct_io_get_blocks/ext3_writepages_get_blocks.
Regards
Suparna
>
> Thanks,
> Mingming
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
> _______________________________________________
> Ext2-devel mailing list
> Ext2-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ext2-devel
--
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Lab, India
prev parent reply other threads:[~2005-04-30 16:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1113220089.2164.52.camel@sisko.sctweedie.blueyonder.co.uk>
[not found] ` <1113244710.4413.38.camel@localhost.localdomain>
[not found] ` <1113249435.2164.198.camel@sisko.sctweedie.blueyonder.co.uk>
[not found] ` <1113288087.4319.49.camel@localhost.localdomain>
[not found] ` <1113304715.2404.39.camel@sisko.sctweedie.blueyonder.co.uk>
[not found] ` <1113348434.4125.54.camel@dyn318043bld.beaverton.ibm.com>
[not found] ` <1113388142.3019.12.camel@sisko.sctweedie.blueyonder.co.uk>
[not found] ` <1114207837.7339.50.camel@localhost.localdomain>
[not found] ` <1114659912.16933.5.camel@mindpipe>
[not found] ` <1114715665.18996.29.camel@localhost.localdomain>
2005-04-29 13:52 ` [Ext2-devel] [RFC] Adding multiple block allocation Suparna Bhattacharya
2005-04-29 17:10 ` Mingming Cao
2005-04-29 19:42 ` Mingming Cao
2005-04-29 20:57 ` Andrew Morton
2005-04-29 21:12 ` Mingming Cao
2005-04-29 21:34 ` Andrew Morton
2005-04-30 16:00 ` [Ext2-devel] " Suparna Bhattacharya
2005-04-29 18:45 ` Badari Pulavarty
2005-04-29 23:22 ` Mingming Cao
2005-04-30 16:10 ` Suparna Bhattacharya
2005-04-30 17:11 ` [Ext2-devel] " Suparna Bhattacharya
2005-04-30 18:07 ` Mingming Cao
2005-05-02 4:46 ` Suparna Bhattacharya
2005-04-30 16:52 ` Suparna Bhattacharya
2005-04-30 0:33 ` Mingming Cao
2005-04-30 0:44 ` Mingming Cao
2005-04-30 17:03 ` Suparna Bhattacharya [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=20050430170331.GE3941@in.ibm.com \
--to=suparna@in.ibm.com \
--cc=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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).