From: "Matias Bjørling" <m@bjorling.me>
To: Ming Lin-SSI <ming.l@ssi.samsung.com>, Jens Axboe <axboe@fb.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 1/6] block: add support for carrying a stream ID in a bio
Date: Wed, 25 Mar 2015 09:11:14 +0100 [thread overview]
Message-ID: <55126DA2.5010004@bjorling.me> (raw)
In-Reply-To: <3A47B4705F6BE24CBB43C61AA73286215067DA@SSIEXCH-MB3.ssi.samsung.com>
>> Pushing it higher is not a big deal as far as the implementation goes, though
>> 16 bits might be stealing a bit too much space for this. On 32-bit archs, we
>> have 18 bits currently free that we can abuse. The Samsung device supports
>> 16 streams. That's honestly a lot more than I would expect most devices to
>> support in hardware, 16 is a lot of open erase blocks and write append points.
>> Obviously the open channel effort would make that more feasible, though.
>
> Can we use 8 bits at least? I'll test performance with 16 streams.
>
Ming, can you provide an example of how streams will be managed for
multiple applications? I can see how it would be efficient for a single
application, but how will it be managed for multiple applications?
-Matias
next prev parent reply other threads:[~2015-03-25 8:11 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 15:26 [PATCH RFC] Support for write stream IDs Jens Axboe
2015-03-24 15:26 ` [PATCH 1/6] block: add support for carrying a stream ID in a bio Jens Axboe
2015-03-24 17:11 ` Matias Bjørling
2015-03-24 17:26 ` Jens Axboe
2015-03-24 17:26 ` Jens Axboe
2015-03-24 22:07 ` Ming Lin-SSI
2015-03-25 1:42 ` Jens Axboe
2015-03-25 1:42 ` Jens Axboe
2015-03-25 8:11 ` Matias Bjørling [this message]
2015-03-25 18:36 ` Ming Lin-SSI
2015-03-25 2:30 ` Dave Chinner
2015-04-12 10:42 ` Dmitry Monakhov
2015-03-24 15:26 ` [PATCH 2/6] Add support for per-file stream ID Jens Axboe
2015-03-24 15:27 ` [PATCH 3/6] direct-io: add support for write stream IDs Jens Axboe
2015-03-25 2:43 ` Dave Chinner
2015-03-25 14:26 ` Jens Axboe
2015-04-10 23:50 ` Ming Lin
2015-04-11 0:06 ` Ming Lin
2015-04-11 11:59 ` Dave Chinner
2015-04-17 6:20 ` Ming Lin
2015-04-17 23:06 ` Dave Chinner
2015-04-17 23:11 ` Jens Axboe
2015-04-17 23:51 ` Dave Chinner
2015-04-18 2:00 ` Jens Axboe
2015-04-17 15:17 ` Jens Axboe
2015-03-24 15:27 ` [PATCH 4/6] Add stream ID support for buffered writeback Jens Axboe
2015-03-25 2:40 ` Dave Chinner
2015-03-25 14:17 ` Jens Axboe
2015-03-24 15:27 ` [PATCH 5/6] btrfs: add support for buffered writeback stream ID Jens Axboe
2015-03-24 15:27 ` [PATCH 6/6] xfs: " Jens Axboe
2015-03-25 2:41 ` Dave Chinner
2015-03-24 17:03 ` [PATCH RFC] Support for write stream IDs Jeff Moyer
2015-03-24 17:08 ` Jens Axboe
2015-03-24 21:46 ` Ming Lin-SSI
2015-03-24 21:48 ` 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=55126DA2.5010004@bjorling.me \
--to=m@bjorling.me \
--cc=axboe@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.l@ssi.samsung.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 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.