From: Jeff Moyer <jmoyer@redhat.com>
To: Saugata Das <saugata.das@stericsson.com>
Cc: <linux-ext4@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<patches@linaro.org>, <arnd.bergmann@linaro.org>,
<venkat@linaro.org>, <lporzio@micron.com>, <tytso@mit.edu>,
<adilger@dilger.ca>, <hch@infradead.org>, <bharrosh@panasas.com>,
<deepak.saxena@linaro.org>, Saugata Das <saugata.das@linaro.org>
Subject: Re: [PATCH v2 1/2] block: add BH_Meta flag
Date: Tue, 22 May 2012 12:37:54 -0400 [thread overview]
Message-ID: <x4962bouq71.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <1337257290-28547-1-git-send-email-saugata.das@stericsson.com> (Saugata Das's message of "Thu, 17 May 2012 17:51:29 +0530")
Saugata Das <saugata.das@stericsson.com> writes:
> From: Saugata Das <saugata.das@linaro.org>
>
> Today, storage devices like eMMC has special features like data tagging
> (introduced in MMC-4.5 version) in order to improve performance of some
> specific writes. On MMC stack, data tagging is used for all writes which
> has REQ_META flag set. This patch adds the capability to add REQ_META flag
> during meta data write.
Presumably you're doing this to get better performance for some
workload, yes? Could you please let us know what workloads you tested
and how this patch set helps? In other words, what benchmarking did you
perform and what were the results? Do you expect this to make some
other workloads perform worse?
Cheers,
Jeff
next prev parent reply other threads:[~2012-05-22 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 12:21 [PATCH v2 1/2] block: add BH_Meta flag Saugata Das
2012-05-17 12:21 ` [PATCH v2 2/2] ext4: annotate all meta data requests Saugata Das
2012-05-22 4:18 ` [PATCH v2 1/2] block: add BH_Meta flag Saugata Das
2012-05-22 16:37 ` Jeff Moyer [this message]
2012-05-28 14:30 ` Saugata Das
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=x4962bouq71.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=adilger@dilger.ca \
--cc=arnd.bergmann@linaro.org \
--cc=bharrosh@panasas.com \
--cc=deepak.saxena@linaro.org \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lporzio@micron.com \
--cc=patches@linaro.org \
--cc=saugata.das@linaro.org \
--cc=saugata.das@stericsson.com \
--cc=tytso@mit.edu \
--cc=venkat@linaro.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;
as well as URLs for NNTP newsgroup(s).