mmc: remove bondage between REQ_META and reliable write
Anytime a write operation is performed with Reliable Write flag enabled,
the eMMC device is enforced to bypass the cache and do a write to the
underling NVM device by Jedec specification; this causes a performance
penalty since write opera
Sorry I used a wrong email/patch format.
Reposting the patch using the correct format.
>From: Luca Porzio (lporzio)
>Sent: Friday, 06 November, 2015 12:23
>To: Ulf Hansson (ulf.hans...@linaro.org); 'linux-mmc@vger.kernel.org'
>Cc: Bruce Ford (bford); Alex Lemberg; &#x
Alex, Ulf,
I am not sure about the status of this patch.
Still I would like to give some feedback.
The Jedec specification requires to check the
PRODUCTION_STATE_AWARENESS_ENABLEMENT (ext_csd[17])
register before issuing a PSA command.
Actually in some devices the PSA register might be a
"don'
Jaehoon,
The sleep notification according to Jedec specification, requires
one of the voltages not to be cut.
Within this patch I do not see any difference with current
implementation of power off notification.
In other words: does this patch cut both Vcc and VccQ?
Where is the code to control
Maya,
This looks good to me.
Thanks,
Luca
> -Original Message-
> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
> ow...@vger.kernel.org] On Behalf Of me...@codeaurora.org
> Sent: Wednesday, May 01, 2013 9:44 AM
> To: Maya Erez
> Cc: linux-mmc@vger.kernel.org; linux-arm-...@v
Looks good to me.
Thanks Maya.
> -Original Message-
> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
> ow...@vger.kernel.org] On Behalf Of Maya Erez
> Sent: Thursday, April 18, 2013 2:42 PM
> To: linux-mmc@vger.kernel.org
> Cc: linux-arm-...@vger.kernel.org; Maya Erez; Yaniv Gar
Hi Maya,
> -Original Message-
> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
> ow...@vger.kernel.org] On Behalf Of Maya Erez
> Sent: Wednesday, April 17, 2013 1:39 PM
> To: linux-mmc@vger.kernel.org
> Cc: linux-arm-...@vger.kernel.org; Maya Erez; Yaniv Gardi; open list
> Subjec
mmc-ow...@vger.kernel.org [mailto:linux-mmc-
> ow...@vger.kernel.org] On Behalf Of me...@codeaurora.org
> Sent: Thursday, March 21, 2013 8:50 PM
> To: Luca Porzio (lporzio)
> Cc: Yaniv Gardi; linux-mmc@vger.kernel.org; vgo...@redhat.com;
> t...@kernel.org; linux-ker...@vger.
Hi Yaniv,
> -Original Message-
> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
> ow...@vger.kernel.org] On Behalf Of Yaniv Gardi
> Sent: Sunday, February 24, 2013 12:39 PM
> To: linux-mmc@vger.kernel.org; vgo...@redhat.com; t...@kernel.org; linux-
> ker...@vger.kernel.org
> Cc:
Saugata Das; linux-
> e...@vger.kernel.org; linux-fsde...@vger.kernel.org; linux-
> m...@vger.kernel.org; patc...@linaro.org; ven...@linaro.org; Luca Porzio
> (lporzio)
> Subject: Re: [PATCH 2/3] ext4: Context support
>
> On Wed, 2012-06-13 at 19:44 +, Arnd Bergmann wrote:
> > I t
rg; linux-fsde...@vger.kernel.org; linux-
> m...@vger.kernel.org; patc...@linaro.org; ven...@linaro.org; Luca Porzio
> (lporzio)
> Subject: Re: [PATCH 2/3] ext4: Context support
>
> On Monday 18 June 2012, Ted Ts'o wrote:
> > On Sat, Jun 16, 2012 at 05:41:23PM +, Arnd B
Hallo Subhash,
One general comment: native sector size is mandatory (as of Jedec spec)
for >256GB devices. For other devices native sector size is optional.
This feature is not meant for performance improvement. Anyway if you
start using your device with 4K alignment, you should already see
som
an Kim; linaro-ker...@lists.linaro.org; android-
> ker...@googlegroups.com; linux...@kvack.org; Luca Porzio (lporzio); Alex
> Lemberg; linux-ker...@vger.kernel.org; Saugata Das; Venkatraman S; Yejin Moon;
> Hyojin Jeong; linux-mmc@vger.kernel.org
> Subject: Re: swap on eMMC and other flash
>
> I
'Rik van Riel';
> linux-mmc@vger.kernel.org; linux-ker...@vger.kernel.org; Luca Porzio
> (lporzio); linux...@kvack.org; kernel-t...@android.com; 'Yejin Moon'; 'Hugh
> Dickins'; 'Yaniv Iarovici'; c...@samsung.com
> Subject: Re: swap on eMMC and other f
Hi,
>
> Yes, this makes sense. With current implementation, mmc_select_powerclass()
> should never really fail which means failure should be treated as fatal and
> we should really skip the card initialization.
> This patch is already pushed to mmc-next. So I will post another patch (by
> next we
Hi Adrian,
> The sanitize logic looks wrong to me. I would expect it to look
> like this:
>
>
> diff --git a/drivers/mmc/card/block.c b/drivers/mmc/card/block.c
> index b180965..f5e0534 100644
> --- a/drivers/mmc/card/block.c
> +++ b/drivers/mmc/card/block.c
> @@ -881,17 +881,12 @@ static int m
Hugh,
Great topics. As per one of Rik original points:
> 4) skip writeout of zero-filled pages - this can be a big help
> for KVM virtual machines running Windows, since Windows zeroes
> out free pages; simply discarding a zero-filled page is not
> at all simple in the current VM, w
17 matches
Mail list logo
