linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Emil Lenngren <emil.lenngren@gmail.com>
Cc: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>,
	linux-mtd <linux-mtd@lists.infradead.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Michele Dionisio <michele.dionisio@gmail.com>
Subject: Re: [PATCH] ubifs: Add support for zstd compression.
Date: Sat, 8 Jun 2019 10:46:54 +0200 (CEST)	[thread overview]
Message-ID: <2132182687.85021.1559983614464.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAO1O6seVp0wBVE6AKmu+EYhoghxbErNuK1F=Y5ewzD=CRro24g@mail.gmail.com>

----- Ursprüngliche Mail -----
> ARM Cortex-A7. The kernel is compiled with gcc 7.3.1. Next week I'll
> test some more.

Good to know!

> I have a question about how the decompression is done while reading.
> When a large file is read from the filesystem (assuming not in any
> cache), is it the case that first a chunk is read from flash, that
> chunk is then decompressed, later next chunk is read from flash, that
> one is then decompressed and so on, or can the decompression be done
> in parallel while reading the next chunk from flash?

No, this is a serial operation.

Thanks,
//richard

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

      reply	other threads:[~2019-06-08  8:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 21:02 [PATCH] ubifs: Add support for zstd compression Richard Weinberger
2019-05-16 18:23 ` Sebastian Andrzej Siewior
2019-06-07 15:34 ` Emil Lenngren
2019-06-07 20:09   ` Richard Weinberger
2019-06-07 20:27     ` Emil Lenngren
2019-06-07 20:49       ` Richard Weinberger
2019-06-07 23:40         ` Emil Lenngren
2019-06-08  8:46           ` 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=2132182687.85021.1559983614464.JavaMail.zimbra@nod.at \
    --to=richard@nod.at \
    --cc=emil.lenngren@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michele.dionisio@gmail.com \
    --cc=sebastian@breakpoint.cc \
    /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).