mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: john.hubbard@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	John Hubbard <jhubbard@nvidia.com>, Sage Weil <sage@redhat.com>,
	Ilya Dryomov <idryomov@gmail.com>,
	ceph-devel@vger.kernel.org
Subject: Re: [PATCH] fs/ceph: use release_pages() directly
Date: Fri, 09 Aug 2019 07:24:59 -0400	[thread overview]
Message-ID: <368e0c787cc9d0c0d99121f8f1b03c45e1a93f08.camel@kernel.org> (raw)
In-Reply-To: <20190809035647.18866-1-jhubbard@nvidia.com>

On Thu, 2019-08-08 at 20:56 -0700, john.hubbard@gmail.com wrote:
> From: John Hubbard <jhubbard@nvidia.com>
> 
> release_pages() has been available to modules since Oct, 2010,
> when commit 0be8557bcd34 ("fuse: use release_pages()") added
> EXPORT_SYMBOL(release_pages). However, this ceph code was still
> using a workaround.
> 
> Remove the workaround, and call release_pages() directly.
> 
> Cc: Jeff Layton <jlayton@kernel.org>
> Cc: Sage Weil <sage@redhat.com>
> Cc: Ilya Dryomov <idryomov@gmail.com>
> Cc: ceph-devel@vger.kernel.org
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> ---
> 
> Hi,
> 
> I noticed this while I trying to understand mlock.c's use of
> pagevec_release(). So I was looking around for examples, and stumbled
> across this, which seems worth cleaning up.
> 
> thanks,
> John Hubbard
> NVIDIA
> 
>  fs/ceph/addr.c | 19 +------------------
>  1 file changed, 1 insertion(+), 18 deletions(-)
> 
> diff --git a/fs/ceph/addr.c b/fs/ceph/addr.c
> index e078cc55b989..22ed45d143be 100644
> --- a/fs/ceph/addr.c
> +++ b/fs/ceph/addr.c
> @@ -679,23 +679,6 @@ static int ceph_writepage(struct page *page, struct writeback_control *wbc)
>  	return err;
>  }
>  
> -/*
> - * lame release_pages helper.  release_pages() isn't exported to
> - * modules.
> - */
> -static void ceph_release_pages(struct page **pages, int num)
> -{
> -	struct pagevec pvec;
> -	int i;
> -
> -	pagevec_init(&pvec);
> -	for (i = 0; i < num; i++) {
> -		if (pagevec_add(&pvec, pages[i]) == 0)
> -			pagevec_release(&pvec);
> -	}
> -	pagevec_release(&pvec);
> -}
> -
>  /*
>   * async writeback completion handler.
>   *
> @@ -769,7 +752,7 @@ static void writepages_finish(struct ceph_osd_request *req)
>  		dout("writepages_finish %p wrote %llu bytes cleaned %d pages\n",
>  		     inode, osd_data->length, rc >= 0 ? num_pages : 0);
>  
> -		ceph_release_pages(osd_data->pages, num_pages);
> +		release_pages(osd_data->pages, num_pages);
>  	}
>  
>  	ceph_put_wrbuffer_cap_refs(ci, total_pages, snapc);

Thanks John. Running tests on it now, and will probably push to our
testing branch later today. It should make v5.4.

-- 
Jeff Layton <jlayton@kernel.org>


      reply	other threads:[~2019-08-09 11:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09  3:56 john.hubbard
2019-08-09 11:24 ` Jeff Layton [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=368e0c787cc9d0c0d99121f8f1b03c45e1a93f08.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=idryomov@gmail.com \
    --cc=jhubbard@nvidia.com \
    --cc=john.hubbard@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sage@redhat.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

all inboxes | Powered by JetHome®