From: keith.busch@intel.com (Keith Busch)
Subject: Weirdness with discard cmd and get log pages
Date: Thu, 13 Oct 2016 12:15:19 -0400 [thread overview]
Message-ID: <20161013161519.GE17823@localhost.localdomain> (raw)
In-Reply-To: <CAG3=cOkxyNq3heevOOpOMcezTsEktPfsoWAEVjWdTA28KgVwAg@mail.gmail.com>
On Thu, Oct 13, 2016@08:46:30AM -0700, Nisha Miller wrote:
> In the case of discard command, we are able to fetch the first two
> ranges (i.e 16 bytes/range x 2) correctly using DMA. But any ranges
> after that contain just junk data. For example, if we try to fetch 4
> ranges, ranges 1-2 are valid but ranges 3-4 contain junk.
How did you set up a discard command with more than one range? The
standard discard path to the driver allows only one.
next prev parent reply other threads:[~2016-10-13 16:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 15:46 Weirdness with discard cmd and get log pages Nisha Miller
2016-10-13 16:15 ` Keith Busch [this message]
2016-10-13 18:18 ` Nisha Miller
2016-10-13 23:18 ` Keith Busch
2016-10-14 17:44 ` Keith Busch
2016-10-14 21:33 ` Nisha Miller
2016-10-14 23:19 ` Keith Busch
2016-10-18 16:55 ` Nisha Miller
2016-10-18 17:08 ` Keith Busch
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=20161013161519.GE17823@localhost.localdomain \
--to=keith.busch@intel.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