From: Jens Axboe <axboe@fb.com>
To: Ming Lin <ming.l@samsung.com>, <linux-kernel@vger.kernel.org>
Cc: <linux-fsdevel@vger.kernel.org>, <david@fromorbit.com>,
Changho Choi-SSI <changho.c@ssi.samsung.com>,
"Kwan (Hingkwan) Huen-SSI" <kwan.huen@ssi.samsung.com>
Subject: Re: [RFC DRAFT PATCH] per-buffered-write stream IDs
Date: Tue, 21 Apr 2015 11:12:50 -0600 [thread overview]
Message-ID: <55368512.1020503@fb.com> (raw)
In-Reply-To: <1429636187-30236-1-git-send-email-ming.l@samsung.com>
On 04/21/2015 11:09 AM, Ming Lin wrote:
> Hi Jens,
>
> This RFC DRAFT patch is on top of your "[PATCH v2] Support for write stream IDs"
> I throw it out early to get comments if it's the way to go.
>
> Quote LWN(http://lwn.net/Articles/638722):
>
> "There would be clear value in a closer association between stream IDs
> and specific buffered-write operations. Getting there would require storing
> the stream ID with each dirtied page, though; that, in turn, almost certainly
> implies shoehorning the stream ID into the associated page structure.
> That would not be an easy task; it is not surprising that it is not a part of
> this patch set. Should the lack of per-buffered-write stream IDs prove to be
> a serious constraint in the future, somebody will certainly be motivated to
> try to find a place to store another eight bits in struct page."
>
> This draft patch stores stream_id in buffer head instead of page.
This is pointless. You need to store it in the page, if the whole point
is that you want this to be trackable. And adding it to struct page
would be a no-go, we can't increase the size of that. See various other
discussions around, for instance, IO priorities for buffered writeback
and tracking that state on the side.
--
Jens Axboe
next prev parent reply other threads:[~2015-04-21 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 17:09 [RFC DRAFT PATCH] per-buffered-write stream IDs Ming Lin
2015-04-21 17:12 ` Jens Axboe [this message]
2015-04-21 18:34 ` Ming Lin
2015-04-21 19:05 ` Jens Axboe
2015-04-22 13:57 ` Jan Kara
2015-04-22 15:56 ` 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=55368512.1020503@fb.com \
--to=axboe@fb.com \
--cc=changho.c@ssi.samsung.com \
--cc=david@fromorbit.com \
--cc=kwan.huen@ssi.samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.l@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.