All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: cmm@us.ibm.com, sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH -v2] ext4: Use inode preallocation with -o noextents
Date: Fri, 6 Jun 2008 21:56:33 +0530	[thread overview]
Message-ID: <20080606162633.GA22364@skywalker> (raw)
In-Reply-To: <20080605153701.GB25477@mit.edu>

On Thu, Jun 05, 2008 at 11:37:01AM -0400, Theodore Tso wrote:
> On Thu, Jun 05, 2008 at 02:13:29PM +0530, Aneesh Kumar K.V wrote:
> > 
> > Something like below ? . I will send a final patch once I get the
> > patchqueu updated. I am not able to reach repo.or.cz currently.
> 
> This is better, but it still means that we are exporting a large
> number of functions to the callers.  It's not clear to me we need so
> many different variants of ext4_new_blocks_* --- what is their
> justification to exist?
> 
> For example, why not just have:
> 
> static ext4_fsblk_t ext4_new_blocks(handle_t *handle, struct inode *inode,
>        				ext4_lblk_t iblock, ext4_fsblk_t goal,
> 				unsigned long *count, int *errp, int meta)
> 

Now that we have moved all the code to do_blk_alloc, we can be assured
that we won't miss bug fixes to those allocation APIs when fixing one of
them. IMHO having separate APIs reduces the risk of misusing them

-aneesh

      parent reply	other threads:[~2008-06-06 16:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-19 20:34 [PATCH -v2] ext4: Use inode preallocation with -o noextents Aneesh Kumar K.V
2008-06-04  2:23 ` Theodore Tso
2008-06-04  4:01   ` Aneesh Kumar K.V
2008-06-05  3:22     ` Theodore Tso
2008-06-05  8:43       ` Aneesh Kumar K.V
2008-06-05 14:55         ` Mingming Cao
2008-06-05 18:24           ` Andreas Dilger
2008-06-05 18:46             ` Aneesh Kumar K.V
2008-06-06 21:33             ` Mingming Cao
2008-06-11  3:26             ` Shen Feng
2008-06-12  9:34               ` Andreas Dilger
2008-06-12 13:41                 ` Eric Sandeen
2008-06-11  3:44           ` Shen Feng
2008-06-16  3:41           ` Shen Feng
2008-06-17  9:42             ` Shen Feng
2008-06-17 10:48               ` Aneesh Kumar K.V
2008-06-18  1:43                 ` Shen Feng
2008-06-05 15:37         ` Theodore Tso
2008-06-05 18:28           ` Andreas Dilger
2008-06-05 19:12             ` Aneesh Kumar K.V
2008-06-05 20:58               ` Andreas Dilger
2008-06-06 16:26           ` Aneesh Kumar K.V [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=20080606162633.GA22364@skywalker \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.