linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: valdis.kletnieks@vt.edu
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
Cc: Adam Borowski <kilobyte@angband.pl>,
	Pintu Agarwal <pintu.ping@gmail.com>,
	linux-mm@kvack.org, open list <linux-kernel@vger.kernel.org>,
	kernelnewbies@kernelnewbies.org
Subject: Re: Creating compressed backing_store as swapfile
Date: Mon, 05 Nov 2018 11:14:23 -0500	[thread overview]
Message-ID: <42594.1541434463@turing-police.cc.vt.edu> (raw)
In-Reply-To: <79d0c96a-a0a2-63ec-db91-42fd349d50c1@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 447 bytes --]

On Mon, 05 Nov 2018 11:07:12 -0500, "Austin S. Hemmelgarn" said:

> Performance isn't _too_ bad for the BTRFS case though (I've actually
> tested this before), just make sure you disable direct I/O mode on the
> loop device, otherwise you run the risk of data corruption.

Did you test that for random-access. or just sequential read/write?
(Also, see the note in my other mail regarding doing a random-access
write to the middle of the file...)


[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]

  reply	other threads:[~2018-11-05 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 15:01 Creating compressed backing_store as swapfile Pintu Agarwal
2018-11-05 15:58 ` Adam Borowski
2018-11-05 16:07   ` Austin S. Hemmelgarn
2018-11-05 16:14     ` valdis.kletnieks [this message]
2018-11-05 16:28       ` Austin S. Hemmelgarn
2018-11-05 16:53         ` valdis.kletnieks
2018-11-05 16:55           ` Austin S. Hemmelgarn
2018-11-08  9:51     ` Pintu Agarwal
2018-11-05 16:12 ` valdis.kletnieks
2018-11-08  9:46   ` Pintu Agarwal

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=42594.1541434463@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=ahferroin7@gmail.com \
    --cc=kernelnewbies@kernelnewbies.org \
    --cc=kilobyte@angband.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pintu.ping@gmail.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).