From: Maksim Fomin <maxim@fomin.one>
To: Andrei Borzenkov <arvidjaar@gmail.com>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Hibernation into swap file
Date: Thu, 09 May 2019 17:04:11 +0000 [thread overview]
Message-ID: <hHUq9SQfm-rxaa4ZlD815Pm8OwYY7CyglT0TcRVbm42v1fZrsadaNN_sDoxqXrmf55CcYmbWXKuYMEd1Unve5HVTXK-qchse-p9rfs0JYG4=@fomin.one> (raw)
In-Reply-To: <60258f5c-e78e-da10-fa19-29038803e160@gmail.com>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, May 9, 2019 6:13 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
> I think we need to allow at least some amount of trust to developers and
> expect that this feature would not be released if it had such an obvious
> problem.
>
> Of course bug happens and it surely needs wider testing.
>
> > Best regards,
> > Maksim Fomin
Nowhere in this thread I critiqued developers for releasing btrfs with obvious problems.
What was released is 'swap file support' (from changelog). This does not necessarily mean 'swap file hibernation support'. That's why I asked question about this. After receiving answers here and reading linux/systemd bugzilla, I decided that I am not interested in hibernation in swap file because its costs outweigh my potential benefits. This has nothing to do with trust.
Best regards,
Maksim Fomin
next prev parent reply other threads:[~2019-05-09 17:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 7:50 Hibernation into swap file Maksim Fomin
2019-05-05 9:08 ` Andrei Borzenkov
2019-05-06 5:40 ` Chris Murphy
2019-05-06 18:25 ` Maksim Fomin
2019-05-09 6:13 ` Andrei Borzenkov
2019-05-09 17:04 ` Maksim Fomin [this message]
2019-05-06 11:32 ` David Sterba
2020-01-23 17:20 ` Chris Murphy
2020-01-24 4:03 ` Andrei Borzenkov
2020-01-27 19:25 ` Omar Sandoval
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='hHUq9SQfm-rxaa4ZlD815Pm8OwYY7CyglT0TcRVbm42v1fZrsadaNN_sDoxqXrmf55CcYmbWXKuYMEd1Unve5HVTXK-qchse-p9rfs0JYG4=@fomin.one' \
--to=maxim@fomin.one \
--cc=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.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;
as well as URLs for NNTP newsgroup(s).