From: Jeff Moyer <jmoyer@redhat.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Grant Grundler <grundler@chromium.org>,
Jens Axboe <axboe@kernel.dk>,
"linux-mmc\@vger.kernel.org" <linux-mmc@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Gwendal Grignou <gwendal@chromium.org>
Subject: Re: RFC: 32-bit __data_len and REQ_DISCARD+REQ_SECURE
Date: Wed, 28 Oct 2015 18:15:51 -0400 [thread overview]
Message-ID: <x49pozyljvs.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <CAPDyKFpXtio5m6V1M5QQcB1RNt4JtoDZ2qL2FqLDDNV4aODVAg@mail.gmail.com> (Ulf Hansson's message of "Wed, 21 Oct 2015 11:00:57 +0200")
Ulf Hansson <ulf.hansson@linaro.org> writes:
> I am not sure if this issue is the same as been discussed earlier on
> the mmc list regarding "discard/erase".
>
> Anyway, there have been several attempts to fix bugs related to this.
> One of these discussion kind of pointed out a viable solution, but
> unfortunate no patches that adopts that solution have been posted yet.
>
> You might want to read up on this.
> https://www.mail-archive.com/linux-mmc@vger.kernel.org/msg23643.html
> http://linux-mmc.vger.kernel.narkive.com/Wp31G953/patch-mmc-core-don-t-return-1-for-max-discard
>
> So this is an old issue, which should have been fixed long long long time ago...
Thanks Ulf. After reading all of the linked discussions, it's my
understanding that this is an emmc-specific issue that doesn't require
any block layer changes. If that's wrong, please let me know.
Cheers,
Jeff
next prev parent reply other threads:[~2015-10-28 22:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 1:54 Grant Grundler
2015-09-24 17:39 ` Grant Grundler
[not found] ` <CANEJEGukOKUgRJNPVaeEXpx-REzj8ooSfWdrnRMMCQr6EVaNqQ@mail.gmail.com>
2015-09-28 21:45 ` Fwd: " Grant Grundler
2015-09-29 12:56 ` Gwendal Grignou
2015-10-20 17:53 ` Grant Grundler
2015-10-20 18:57 ` Jeff Moyer
2015-10-21 9:00 ` Ulf Hansson
2015-10-21 17:06 ` Grant Grundler
2015-10-28 22:15 ` Jeff Moyer [this message]
2016-06-02 22:56 ` [PATCH] mmc: Set pref erase size based on size Gwendal Grignou
2016-06-03 0:27 ` [PATCH v2] " Gwendal Grignou
2016-06-03 16:08 ` [PATCH v3] CHROMIUM: " Gwendal Grignou
2016-06-22 15:23 ` Ulf Hansson
2016-06-10 17:02 ` [PATCH v2] " Grant Grundler
2015-10-21 17:38 ` RFC: 32-bit __data_len and REQ_DISCARD+REQ_SECURE Grant Grundler
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=x49pozyljvs.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@kernel.dk \
--cc=grundler@chromium.org \
--cc=gwendal@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--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
all inboxes | Powered by JetHome®