stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: Alex Shi <alex.shi@linaro.org>
Cc: Jan Kara <jack@suse.cz>, Dmitry Monakhov <dmonakhov@openvz.org>,
	Theodore Ts'o <tytso@mit.edu>,
	Linaro Kernel <linaro-kernel@lists.linaro.org>,
	stable@vger.kernel.org, Mark Brown <broonie@linaro.org>
Subject: Re: a old issue of ext4 on lts 3.10
Date: Thu, 21 May 2015 09:51:59 -0700	[thread overview]
Message-ID: <20150521165159.GA12861@kroah.com> (raw)
In-Reply-To: <555DA53C.3070707@linaro.org>

On Thu, May 21, 2015 at 05:28:28PM +0800, Alex Shi wrote:
> Hi Greg,
> 
> It was reported this commit could save few seconds sometime in
> consequence writing on smart phone.
> 
> commit 7afe5aa59ed3da7b6161617e7f157c7c680dc41e
>     ext4: convert write_begin methods to stable_page_writes semantics
> 
> > The patch helps because most of storage today doesn't require that the
> > page isn't changed while IO is in flight. That is required only for
> > data checksumming or copy-on-write semantics but ext4 does neither of
> > those. So we don't have to wait for IO completion in ext4_write_begin()
> > unless underlying storage requires it.
> >
> > 								Honza
> 
> Seems it is a very simple and useful patch for some stable kernel, like
> lts 3.10. Would you like to pick it up?

If Jan and Ted say it's ok, I'll queue it up.

Have you tried this patch and verified that it does fix an issue and is
measurable?

thanks,

greg k-h

  reply	other threads:[~2015-05-21 16:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 14:40 a old issue of ext4 on lts 3.10 Alex Shi
2015-05-14 20:36 ` Dmitry Monakhov
2015-05-17 15:19   ` Alex Shi
2015-05-18  6:41     ` Jan Kara
2015-05-20  3:04       ` Alex Shi
2015-05-18  6:21   ` Jan Kara
2015-05-20  2:58     ` Alex Shi
2015-05-21  9:28     ` Alex Shi
2015-05-21 16:51       ` gregkh [this message]
2015-05-22  8:26         ` Jan Kara
2015-05-24  2:54         ` Alex Shi

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=20150521165159.GA12861@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alex.shi@linaro.org \
    --cc=broonie@linaro.org \
    --cc=dmonakhov@openvz.org \
    --cc=jack@suse.cz \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=stable@vger.kernel.org \
    --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 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).