From: Richard Weinberger <richard.weinberger@gmail.com>
To: Stanley Chu <stanley.chu@mediatek.com>
Cc: linger.lee@mediatek.com, Artem Bityutskiy <dedekind1@gmail.com>,
Richard Weinberger <richard@nod.at>,
kuohong.wang@mediatek.com,
Adrian Hunter <adrian.hunter@intel.com>,
linux-mtd@lists.infradead.org, chienwei.chang@mediatek.com,
matthias.bgg@gmail.com, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1] ubifs: support page statistics in vmstat
Date: Mon, 16 Sep 2019 00:05:23 +0200 [thread overview]
Message-ID: <CAFLxGvxG3rhr6w7xNthJco1nHgZgGhw+cda0anHuNz4OdD7ntw@mail.gmail.com> (raw)
In-Reply-To: <CAFLxGvwLTTN+S=Bd0gZWKJbjvanCe_HV_dfmoZzyb1hzWkkGpQ@mail.gmail.com>
On Sun, Jul 21, 2019 at 10:15 PM Richard Weinberger
<richard.weinberger@gmail.com> wrote:
>
> On Thu, Jul 18, 2019 at 2:04 PM Stanley Chu <stanley.chu@mediatek.com> wrote:
> >
> > Currently PGPGIN and PGPGOUT statistics in vmstat is only
> > hooked in submit_bio() for block device I/O path.
> >
> > This patch adds this feature for ubifs as well.
>
> While I think updating these counter for raw flash makes sense,
> I wonder whether UBIFS is the right layer.
> Why not directly in MTD or at least UBI?
Ping?
--
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-09-15 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 12:03 [PATCH v1] ubifs: support page statistics in vmstat Stanley Chu
2019-07-21 20:15 ` Richard Weinberger
2019-09-15 22:05 ` Richard Weinberger [this message]
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=CAFLxGvxG3rhr6w7xNthJco1nHgZgGhw+cda0anHuNz4OdD7ntw@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=chienwei.chang@mediatek.com \
--cc=dedekind1@gmail.com \
--cc=kuohong.wang@mediatek.com \
--cc=linger.lee@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=richard@nod.at \
--cc=stanley.chu@mediatek.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;
as well as URLs for NNTP newsgroup(s).