From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Aleksei Besogonov <cyberax@amazon.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/2] RFC: iomap-based swap file activation
Date: Wed, 16 May 2018 08:59:28 -0700 [thread overview]
Message-ID: <20180516155928.GE23858@magnolia> (raw)
In-Reply-To: <20180420220815.44160-1-cyberax@amazon.com>
On Fri, Apr 20, 2018 at 10:08:13PM +0000, Aleksei Besogonov wrote:
> This patch set adds iomap-based swap file initialization, this allows
> it to use files with holes on XFS for swap.
Just out of curiosity (well after the fact, sorry...), what's the
motivation for having sparse swap files?
--D
> Aleksei Besogonov (2):
> fs: Add iomap_swap_activate
> xfs: add support for iomap-based swapfile activation
>
> fs/iomap.c | 87 +++++++++++++++++++++++++++++++++++++++++++++++++++
> fs/xfs/xfs_aops.c | 7 +++++
> include/linux/iomap.h | 5 +++
> mm/swapfile.c | 1 +
> 4 files changed, 100 insertions(+)
>
> --
> 2.14.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-05-16 15:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 22:08 [PATCH 0/2] RFC: iomap-based swap file activation Aleksei Besogonov
2018-04-20 22:08 ` Aleksei Besogonov
2018-04-20 22:08 ` [PATCH 1/2] fs: Add iomap_swap_activate Aleksei Besogonov
2018-04-20 22:08 ` Aleksei Besogonov
2018-04-25 21:34 ` kbuild test robot
2018-04-25 21:34 ` kbuild test robot
2018-04-25 21:38 ` kbuild test robot
2018-04-25 21:38 ` kbuild test robot
2018-04-20 22:08 ` [PATCH 2/2] xfs: add support for iomap-based swapfile activation Aleksei Besogonov
2018-04-20 22:08 ` Aleksei Besogonov
2018-04-20 22:25 ` [PATCH 0/2] RFC: iomap-based swap file activation Darrick J. Wong
2018-04-20 22:38 ` Besogonov, Aleksei
2018-05-16 15:59 ` Darrick J. Wong [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=20180516155928.GE23858@magnolia \
--to=darrick.wong@oracle.com \
--cc=cyberax@amazon.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.