All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Lokesh Jaliminche <lokesh.jaliminche@gmail.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
	linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH v6] EXT4: optimizing group search for inode allocation
Date: Mon, 22 Feb 2016 23:04:51 -0500	[thread overview]
Message-ID: <20160223040451.GJ1215@thunk.org> (raw)
In-Reply-To: <20160119060812.GA7158@server_lokesh>

On Tue, Jan 19, 2016 at 11:38:12AM +0530, Lokesh Jaliminche wrote:
> From: Lokesh Nagappa Jaliminche <lokesh.jaliminche@gmail.com>
> Subject: [PATCH] ext4: optimizing group serch for inode allocation
> 
> Added a check at the start of group search loop to
> avoid looping unecessarily in case of empty group.
> This also allow group search to jump directly to
> "found_flex_bg" with "stats" and "group" already set,
> so there is no need to go through the extra steps of
> setting "best_desc" , "best_group" and then break
> out of the loop just to set "stats" and "group" again.
> 
> Signed-off-by: Lokesh Nagappa Jaliminche <lokesh.jaliminche@gmail.com>

Thanks, applied.

						- Ted

      parent reply	other threads:[~2016-02-23  4:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-18 23:32 [PATCH] EXT4: optimizing group serch for inode allocation lokesh jaliminche
2015-12-21 17:27 ` Andreas Dilger
2015-12-26  8:28   ` [PATCH v3] " Lokesh Jaliminche
2015-12-26  8:41   ` [PATCH v3] EXT4: optimizing group search " Lokesh Jaliminche
     [not found]     ` <2DA2ED68-7DD4-425D-8A47-E896E9BF0F4A@dilger.ca>
2016-01-07  0:46       ` [PATCH v4] " Lokesh Jaliminche
2016-01-11 21:13         ` Andreas Dilger
2016-01-16 22:50           ` [PATCH v5] " Lokesh Jaliminche
2016-01-16 23:02           ` Lokesh Jaliminche
2016-01-18 21:50             ` Andreas Dilger
2016-01-19  6:08               ` [PATCH v6] " Lokesh Jaliminche
2016-01-19  7:24                 ` Andreas Dilger
2016-02-23  4:04                 ` Theodore Ts'o [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=20160223040451.GJ1215@thunk.org \
    --to=tytso@mit.edu \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=lokesh.jaliminche@gmail.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 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.