From: Nikita Yushchenko <nikita.yoush@yandex.ru>
To: merez@codeaurora.org
Cc: linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: mmc idle time bkops?
Date: Mon, 16 Mar 2015 22:46:16 +0300 [thread overview]
Message-ID: <55073308.7090501@yandex.ru> (raw)
In-Reply-To: <bdb5de1e1c2c1cfacdf02ba8f44025a3.squirrel@www.codeaurora.org>
Hi Maya.
Thanks for the information.
There are thoughts that missing support for "non-urgent" bkops request
could be reason of unexpected slowdowns of eMMC i/o that customer is
observing. Thus the interest on the current status.
However, no particular projects or needs yet.
Nikita
> Hi Nikita,
>
> The patch got stuck for a while as there was a request to use the runtime
> PM framework for implementing the idle time BKOPs and I didn't have the
> ability to test it back then.
> We plan to re-implement and test in the upcoming few months (aim to July).
> Do you have a need for this feature in an earlier date or it can wait for
> july?
>
> Thanks,
> Maya
>
>> Hi
>>
>> Some months ago, you've been working on "idle time bkops" feature. The
>> latest (v6) sign of this work I could found is [1]
>>
>> [1] https://lkml.org/lkml/2013/4/14/29
>>
>> However this did not land in mainline, also no replies, and no sign of
>> any follow-up... Complete mystery what has happened to this effort :(
>>
>> What is the latest status of "idle time bkops" functionality?
>> Is any working implementation available?
>>
>> TIA,
>> Nikita Yushchenko
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
>
prev parent reply other threads:[~2015-03-16 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 19:34 mmc idle time bkops? Nikita Yushchenko
2015-03-16 19:37 ` merez
2015-03-16 19:46 ` Nikita Yushchenko [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=55073308.7090501@yandex.ru \
--to=nikita.yoush@yandex.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=merez@codeaurora.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 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.