From: keith.busch@intel.com (Keith Busch)
Subject: [PATCHv2] NVMe: Spliting large i/o in the ioctl path [for-linus branch]
Date: Wed, 18 Mar 2015 18:41:15 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1503181833470.32385@localhost.lm.intel.com> (raw)
In-Reply-To: <1424779243-14951-1-git-send-email-sathya.m@samsung.com>
On Tue, 24 Feb 2015, Sathayavathi M wrote:
> + for (count = 0; count < num_split_cmds; count++) {
[snip]
> + c.rw.reftag = cpu_to_le32(io.reftag);
> + c.rw.apptag = cpu_to_le16(io.apptag);
> + c.rw.appmask = cpu_to_le16(io.appmask);
If the reference tag is being used, this needs to be incremented
accoringly in this loop.
Starting to think the ioctl shouldn't even bother correcting users who
request malformed commands.
prev parent reply other threads:[~2015-03-18 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 12:00 [PATCHv2] NVMe: Spliting large i/o in the ioctl path [for-linus branch] Sathayavathi M
2015-03-18 16:21 ` Keith Busch
2015-03-18 18:41 ` Keith Busch [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=alpine.LNX.2.00.1503181833470.32385@localhost.lm.intel.com \
--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