linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Omar Sandoval <osandov@osandov.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com, linux-mm@kvack.org
Subject: Re: [PATCH v7 1/6] mm: split SWP_FILE into SWP_ACTIVATED and SWP_FS
Date: Wed, 19 Sep 2018 11:12:02 -0700	[thread overview]
Message-ID: <20180919181202.GJ479@vader> (raw)
In-Reply-To: <20180919180232.GB18068@cmpxchg.org>

On Wed, Sep 19, 2018 at 02:02:32PM -0400, Johannes Weiner wrote:
> On Tue, Sep 11, 2018 at 03:34:44PM -0700, Omar Sandoval wrote:
> > @@ -2411,8 +2412,10 @@ static int setup_swap_extents(struct swap_info_struct *sis, sector_t *span)
> >  
> >  	if (mapping->a_ops->swap_activate) {
> >  		ret = mapping->a_ops->swap_activate(sis, swap_file, span);
> > +		if (ret >= 0)
> > +			sis->flags |= SWP_ACTIVATED;
> >  		if (!ret) {
> > -			sis->flags |= SWP_FILE;
> > +			sis->flags |= SWP_FS;
> >  			ret = add_swap_extent(sis, 0, sis->max, 0);
> 
> Won't this single, linear extent be in conflict with the discontiguous
> extents you set up in your swap_activate callback in the last patch?

That's only in the case that ->swap_activate() returned 0, which only
nfs_swap_activate() will do. btrfs_swap_activate() and
iomap_swapfile_activate() both return the number of extents they set up.

  reply	other threads:[~2018-09-19 18:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11 22:34 [PATCH v7 0/6] Btrfs: implement swap file support Omar Sandoval
2018-09-11 22:34 ` [PATCH v7 1/6] mm: split SWP_FILE into SWP_ACTIVATED and SWP_FS Omar Sandoval
2018-09-19 18:02   ` Johannes Weiner
2018-09-19 18:12     ` Omar Sandoval [this message]
2018-09-19 18:41       ` Johannes Weiner
2018-10-12 20:59   ` Andrew Morton
2018-10-16 10:20     ` David Sterba
2018-09-11 22:34 ` [PATCH v7 2/6] mm: export add_swap_extent() Omar Sandoval
2018-09-19 18:09   ` Johannes Weiner
2018-09-19 18:28     ` Omar Sandoval
2018-09-19 18:43       ` Johannes Weiner
2018-10-12 20:59   ` Andrew Morton
2018-09-11 22:34 ` [PATCH v7 3/6] vfs: update swap_{,de}activate documentation Omar Sandoval
2018-09-11 22:34 ` [PATCH v7 4/6] Btrfs: prevent ioctls from interfering with a swap file Omar Sandoval
2018-09-11 22:34 ` [PATCH v7 5/6] Btrfs: rename get_chunk_map() and make it non-static Omar Sandoval
2018-09-11 22:34 ` [PATCH v7 6/6] Btrfs: support swap files Omar Sandoval
2018-09-19 17:29 ` [PATCH v7 0/6] Btrfs: implement swap file support 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=20180919181202.GJ479@vader \
    --to=osandov@osandov.com \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-mm@kvack.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).