From: Roman Mamedov <rm@romanrm.net>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Jeff Mahoney <jeffm@suse.com>,
Keith Busch <keith.busch@intel.com>,
Ric Wheeler <ricwheeler@gmail.com>,
Dave Chinner <david@fromorbit.com>,
lsf-pc@lists.linux-foundation.org,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
linux-block@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] More async operations for file systems - async discard?
Date: Fri, 22 Feb 2019 11:15:32 +0500 [thread overview]
Message-ID: <20190222111532.4ead81dc@natsu> (raw)
In-Reply-To: <yq17edsil17.fsf@oracle.com>
On Thu, 21 Feb 2019 22:01:24 -0500
"Martin K. Petersen" <martin.petersen@oracle.com> wrote:
> Consequently, many of the modern devices that claim to support discard
> to make us software folks happy (or to satisfy a purchase order
> requirements) complete the commands without doing anything at all.
> We're simply wasting queue slots.
Any example of such devices? Let alone "many"? Where you would issue a
full-device blkdiscard, but then just read back old data.
I know only one model(PLEXTOR PX-512M6M) of dozens tested, which is peculiar
that it ignores trim specifically for the 1st sector of the entire disk. But
implying there are "many" which no-op it entirely, seems like imagining the
world already works like you would assume it to.
--
With respect,
Roman
next prev parent reply other threads:[~2019-02-22 6:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 20:36 [LSF/MM TOPIC] More async operations for file systems - async discard? Ric Wheeler
2019-02-17 21:09 ` Dave Chinner
2019-02-17 23:42 ` Ric Wheeler
2019-02-18 2:22 ` Dave Chinner
2019-02-18 22:30 ` Ric Wheeler
2019-02-20 23:47 ` Keith Busch
2019-02-21 20:08 ` Dave Chinner
2019-02-21 23:55 ` Jeff Mahoney
2019-02-22 3:01 ` Martin K. Petersen
2019-02-22 6:15 ` Roman Mamedov [this message]
2019-02-22 14:12 ` Martin K. Petersen
2019-02-22 2:51 ` Martin K. Petersen
2019-02-22 16:45 ` Keith Busch
2019-02-27 11:40 ` Ric Wheeler
2019-02-27 13:24 ` Matthew Wilcox
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=20190222111532.4ead81dc@natsu \
--to=rm@romanrm.net \
--cc=david@fromorbit.com \
--cc=jeffm@suse.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=martin.petersen@oracle.com \
--cc=ricwheeler@gmail.com \
/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).