All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niu, Yawei <yawei.niu at intel.com>
To: spdk@lists.01.org
Subject: [SPDK] io size limitation on spdk_blob_io_write()
Date: Thu, 21 Mar 2019 01:36:11 +0000	[thread overview]
Message-ID: <7CD8050B-70F7-453F-AD59-BBDDA1C66585@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 706 bytes --]

Hi,

We discovered that spdk_blob_io_write() will fail with large io size (128MB) over NVMe bdev, I checked the SPDK code a bit, and seems the failure reason is the size exceeded the limitation of NVMe bdev io request size (which depends on the io queue depth & max transfer size).
We may work around to the problem by splitting the io into several spdk_blob_io_write() calls, but I was wondering if blobstore should hide these bdev details/limitations for blobstore caller and split the I/O according to backend bdev limitations (just like what we did for cross cluster boundary io)? So that blobstore caller doesn’t need to differentiate what type of bdev underneath? Any thoughts?

Thanks
-Niu

             reply	other threads:[~2019-03-21  1:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21  1:36 Niu, Yawei [this message]
2019-03-21  7:40 [SPDK] io size limitation on spdk_blob_io_write() Szwed, Maciej
2019-03-21 12:08 Niu, Yawei
2019-03-21 15:47 Harris, James R
2019-03-21 16:40 Niu, Yawei

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=7CD8050B-70F7-453F-AD59-BBDDA1C66585@intel.com \
    --to=spdk@lists.01.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.