linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org, jack@suse.cz,
	aneesh.kumar@linux.vnet.ibm.com, tytso@mit.ed
Subject: Re: [PATCH] ext4: restart ext4_ext_remove_space() after transaction restart
Date: Tue, 25 May 2010 09:55:11 -0400	[thread overview]
Message-ID: <20100525135511.GG5556@thunk.org> (raw)
In-Reply-To: <1271910671-16627-1-git-send-email-dmonakhov@openvz.org>

On Thu, Apr 22, 2010 at 08:31:11AM +0400, Dmitry Monakhov wrote:
> If i_data_sem was internally dropped due to transaction restart, it is
> necessary to restart path look-up because extents tree was possibly
> modified by ext4_get_block().
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=15827
> 
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>

I *think* it would be more efficient to add the additional change:

  	  if (ext4_ext_more_to_rm(path + i)) {

to:

  	  if ((err != -EAGAIN) && ext4_ext_more_to_rm(path + i)) {

in ext4_ext_remove_space() but I would like your opinion...

If we do this optimization I'll probably do it in a separate patch.
It just seems that we're doing a lot of extra work once we fail to
extend the transaction, so it would be good to optimize more of this
out.  It also makes it easier to convince oneself that that all of the
spinning around that happens after returning EAGAIN won't cause any
harm.  After going through the patch carefully I'm pretty sure the
extra work is pointless, but not harmful, but it's better to skip it
entirely if it's not needed.

					 - Ted


      parent reply	other threads:[~2010-05-25 13:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-22  4:31 [PATCH] ext4: restart ext4_ext_remove_space() after transaction restart Dmitry Monakhov
2010-04-22  7:33 ` Dmitry Monakhov
2010-04-26 16:09 ` Jan Kara
2010-05-25 13:32 ` tytso
2010-05-25 14:28   ` Dmitry Monakhov
2010-05-25 21:38     ` tytso
2010-05-26  8:53       ` Dmitry Monakhov
2010-05-25 21:44     ` tytso
2010-05-26  9:12       ` Dmitry Monakhov
2010-05-26 11:51         ` [PATCH] ext4: restart ext4_ext_remove_space() after transaction restart V2 Dmitry Monakhov
2010-05-26 13:23           ` tytso
2010-05-26 13:46             ` Jan Kara
2010-05-26 14:23             ` Dmitry Monakhov
2010-05-26 14:45               ` tytso
2010-05-26 14:47                 ` tytso
2010-05-26 17:22                   ` Dmitry Monakhov
2010-05-25 13:55 ` tytso [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=20100525135511.GG5556@thunk.org \
    --to=tytso@mit.edu \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=dmonakhov@openvz.org \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.ed \
    /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).