From: David Jander <david@protonic.nl>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Pierre Ossman <pierre@ossman.eu>,
Sascha Hauer <s.hauer@pengutronix.de>,
Johan Rudholm <johan.rudholm@axis.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
linux-mmc <linux-mmc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] mmc: core: Optimize case for exactly one erase-group budget TRIM
Date: Fri, 26 Jun 2015 08:56:42 +0200 [thread overview]
Message-ID: <20150626085642.5cdad2e3@archvile> (raw)
In-Reply-To: <CAPDyKFocxYD+q_CQQ4Kz6ZZ88P+DwWcwfrEGEJJEEgkFT5r+MA@mail.gmail.com>
Dear Ulf,
On Thu, 4 Jun 2015 10:31:59 +0200
Ulf Hansson <ulf.hansson@linaro.org> wrote:
> On 3 June 2015 at 10:34, David Jander <david@protonic.nl> wrote:
> > In the (not so unlikely) case that the mmc controller timeout budget is
> > enough for exactly one erase-group, the simplification of allowing one
> > sector has an enormous performance penalty. We optimize this special case
> > by introducing a flag that prohibits erase-group boundary crossing, so
> > that we can allow trimming more than one sector at a time.
> >
> > Signed-off-by: David Jander <david@protonic.nl>
>
> Hi David,
>
> Thanks for working on this!
I have since sent an updated patch that includes more comment. It would be
great if you could find the time to review it. I hope the comments are clear
enough.
Best regards,
--
David Jander
Protonic Holland.
prev parent reply other threads:[~2015-06-26 6:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 8:34 [RFC PATCH] mmc: core: Optimize case for exactly one erase-group budget TRIM David Jander
2015-06-04 8:31 ` Ulf Hansson
2015-06-04 9:42 ` David Jander
2015-06-04 10:20 ` [RFC PATCH 2/2] mmc: core.c: Add comment to clarify special cases of ERASE/TRIM David Jander
2015-06-04 11:16 ` Adrian Hunter
2015-06-04 12:19 ` David Jander
2015-06-26 6:56 ` David Jander [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=20150626085642.5cdad2e3@archvile \
--to=david@protonic.nl \
--cc=adrian.hunter@intel.com \
--cc=javier.martinez@collabora.co.uk \
--cc=johan.rudholm@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=pierre@ossman.eu \
--cc=s.hauer@pengutronix.de \
--cc=ulf.hansson@linaro.org \
/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).