From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jan Kara <jack@suse.cz>
Cc: Changho Choi-SSI <changho.c@ssi.samsung.com>,
"lsf-pc\@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
linux-fsdevel@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] multi-stream IO hint implementation proposal for LSF/MM 2016
Date: Wed, 17 Feb 2016 18:08:04 -0500 [thread overview]
Message-ID: <yq1d1rvvstn.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20160217152155.GA14140@quack.suse.cz> (Jan Kara's message of "Wed, 17 Feb 2016 16:21:55 +0100")
>>>>> "Jan" == Jan Kara <jack@suse.cz> writes:
Jan> So a key question for a feature like this is: How many stream IDs
Jan> are devices going to support? Because AFAIR so far the answer was
Jan> "it depends on the device". However the design how stream IDs can
Jan> be used greatly differs between "a couple of stream IDs" and
Jan> e.g. 2^32 stream IDs. Without this information I don't think the
Jan> discussion would be very useful. So can you provide some rough
Jan> numbers?
Both SCSI and NVMe have a 16-bit stream ID field. So you are capped at
64K unique identifiers.
However, the number of streams a device can have open concurrently is
expected to be much smaller than that. This leaves us with the
interesting problem of how to divide up the available streams. Whether
to support application- and kernel allocated streams concurrently. And
how we deal with explicitly closing streams after use.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2016-02-17 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8F1CD504A027484E89249BCD2A7248DD573D15D9@SSIEXCH-MB3.ssi.samsung.com>
2016-02-17 15:21 ` Jan Kara
2016-02-17 23:08 ` Martin K. Petersen [this message]
2016-02-17 23:36 ` Dave Chinner
[not found] ` <CAJVOszAJTCGzVP7GBx3AQOvUiE7d8-3eMmpmCjPxD4d0+AGX2g@mail.gmail.com>
2016-02-18 10:21 ` Jan Kara
2016-02-18 0:46 ` Jaegeuk Kim
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=yq1d1rvvstn.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=changho.c@ssi.samsung.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®