From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "hans@owltronix.com" <hans@owltronix.com>
Cc: "Johannes.Thumshirn@wdc.com" <Johannes.Thumshirn@wdc.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"slava@dubeyko.com" <slava@dubeyko.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"javier.gonz@samsung.com" <javier.gonz@samsung.com>
Subject: RE: [RFC PATCH] Introduce generalized data temperature estimation framework
Date: Thu, 30 Jan 2025 18:31:47 +0000 [thread overview]
Message-ID: <4907d1ff5cd5a846188b2c9d77d110d926a37ac7.camel@ibm.com> (raw)
In-Reply-To: <CANr-nt0nRZp=g2kbUqd5PoNbH-m9MWd_4x+LmR6x-gTT92MoVQ@mail.gmail.com>
On Wed, 2025-01-29 at 11:23 +0100, Hans Holmberg wrote:
> On Tue, Jan 28, 2025 at 11:31 PM Viacheslav Dubeyko
> <Slava.Dubeyko@ibm.com> wrote:
> >
> >
<skipped>
> > >
> >
> > Another trouble here. What is the way to measure write amplification, from your
> > point of view? Which benchmarking tool or framework do you suggest for write
> > amplification estimation?
>
> FDP drives expose this information. You can retrieve the stats using
> the nvme cli.
Do you mean that FDP drives has some additional info in S.M.A.R.T subsystem?
Does it some special subsystem in FDP drives? Is it regular statistics or some
debug feature of the device?
> If you are using zoned storage, you can add write amp metrics inside
> the file system
> or just measure the amount of blocks written to the device using iostat.
>
I see the point with iostat or blktrace, for example. But what do you imply by
adding write amp metric inside the file system? Especially, if you are
mentioning zoned storage. What is the difference here between conventional and
zoned storage devices?
Thanks,
Slava.
next prev parent reply other threads:[~2025-01-30 18:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 20:24 Viacheslav Dubeyko
2025-01-24 8:19 ` Johannes Thumshirn
2025-01-24 21:03 ` Viacheslav Dubeyko
2025-01-27 14:19 ` Hans Holmberg
2025-01-27 20:58 ` Viacheslav Dubeyko
2025-01-28 8:45 ` Hans Holmberg
2025-01-28 8:59 ` Johannes Thumshirn
2025-01-28 22:35 ` Viacheslav Dubeyko
2025-01-28 22:30 ` Viacheslav Dubeyko
2025-01-29 10:23 ` Hans Holmberg
2025-01-30 18:31 ` Viacheslav Dubeyko [this message]
2025-02-06 8:00 ` Hans Holmberg
2025-01-25 12:25 ` Jeff Layton
2025-01-27 20:12 ` Viacheslav Dubeyko
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=4907d1ff5cd5a846188b2c9d77d110d926a37ac7.camel@ibm.com \
--to=slava.dubeyko@ibm.com \
--cc=Johannes.Thumshirn@wdc.com \
--cc=hans@owltronix.com \
--cc=javier.gonz@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=slava@dubeyko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox