From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Keith Busch <keith.busch@intel.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Jitendra Bhivare <jitendra.bhivare@broadcom.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] block: Fix transfer when chuck sectors exceeds max
Date: Tue, 26 Jun 2018 11:54:18 -0400 [thread overview]
Message-ID: <yq160255ys5.fsf@oracle.com> (raw)
In-Reply-To: <20180626151458.6675-1-keith.busch@intel.com> (Keith Busch's message of "Tue, 26 Jun 2018 09:14:58 -0600")
Keith,
> A device may have boundary restrictions where the number of sectors
> between boundaries exceeds its max transfer size. In this case, we need
> to cap the max size to the smaller of the two limits.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: martin.petersen@oracle.com (Martin K. Petersen)
Subject: [PATCH] block: Fix transfer when chuck sectors exceeds max
Date: Tue, 26 Jun 2018 11:54:18 -0400 [thread overview]
Message-ID: <yq160255ys5.fsf@oracle.com> (raw)
In-Reply-To: <20180626151458.6675-1-keith.busch@intel.com> (Keith Busch's message of "Tue, 26 Jun 2018 09:14:58 -0600")
Keith,
> A device may have boundary restrictions where the number of sectors
> between boundaries exceeds its max transfer size. In this case, we need
> to cap the max size to the smaller of the two limits.
Reviewed-by: Martin K. Petersen <martin.petersen at oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-06-26 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 15:14 [PATCH] block: Fix transfer when chuck sectors exceeds max Keith Busch
2018-06-26 15:14 ` Keith Busch
2018-06-26 15:54 ` Martin K. Petersen [this message]
2018-06-26 15:54 ` Martin K. Petersen
2018-06-26 18:18 ` Jens Axboe
2018-06-26 18:18 ` Jens Axboe
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=yq160255ys5.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=jitendra.bhivare@broadcom.com \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.