public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Pratyush Yadav <pratyush@kernel.org>
Cc: David Oberhollenzer <david.oberhollenzer@sigma-star.at>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH 0/2] Measure read while write latency
Date: Mon, 21 Nov 2022 10:47:10 +0100	[thread overview]
Message-ID: <20221121104710.1fba2a1f@xps-13> (raw)
In-Reply-To: <20221121094020.4ezpibat7az3ya6g@yadavpratyush.com>

Hi Pratyush, David

pratyush@kernel.org wrote on Mon, 21 Nov 2022 10:40:20 +0100:

> On 21/11/22 08:37AM, David Oberhollenzer wrote:
> > Applied to mtd-utils.git master.  
> 
> But SPI NOR does not yet support read-while-write. The patches are still 
> under review [0]. So does this even work? Should mtd-utils test a 
> feature that has not been merged into the driver yet? I think it should 
> not.

I don't mind if the tool gets in first, it won't hurt anyway as:
- no changes are expected if people do not use the new -k option
- if they do, the gained latency will just be 0 (which is a use case of
  the tool: measuring whether or not RWW works/is supported).

> [0] https://lore.kernel.org/linux-mtd/20221110155513.819798-1-miquel.raynal@bootlin.com/T/#mf4fdf32e77b1b21bd30ca01eed999f0efc3db6ee

The only thing is: if the series does not get in for any reason, we'll
have to revert it.

Either ways, I'm fine with it.

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

      reply	other threads:[~2022-11-21  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 15:59 [PATCH 0/2] Measure read while write latency Miquel Raynal
2022-11-10 15:59 ` [PATCH 1/2] mtd-utils: flash_speed: Rework the time counting helpers Miquel Raynal
2022-11-10 15:59 ` [PATCH 2/2] mtd-utils: flash_speed: Measure read while write latency Miquel Raynal
2022-11-21  7:37 ` [PATCH 0/2] " David Oberhollenzer
2022-11-21  9:40   ` Pratyush Yadav
2022-11-21  9:47     ` Miquel Raynal [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=20221121104710.1fba2a1f@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=david.oberhollenzer@sigma-star.at \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pratyush@kernel.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