linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Jennings <rcj@linux.vnet.ibm.com>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-mm@kvack.org, Alexander Viro <viro@zeniv.linux.org.uk>,
	Rik van Riel <riel@redhat.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Matt Helsley <matt.helsley@gmail.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Michael Roth <mdroth@linux.vnet.ibm.com>,
	Lei Li <lilei@linux.vnet.ibm.com>,
	Leonardo Garcia <lagarcia@linux.vnet.ibm.com>
Subject: Re: [RFC PATCH 1/2] vmsplice unmap gifted pages for recipient
Date: Fri, 26 Jul 2013 10:16:21 -0500	[thread overview]
Message-ID: <20130726151621.GA5037@linux.vnet.ibm.com> (raw)
In-Reply-To: <51F160A5.2040004@sr71.net>

* Dave Hansen (dave@sr71.net) wrote:
> On 07/25/2013 10:21 AM, Robert Jennings wrote:
> > +static void zap_buf_page(unsigned long useraddr)
> > +{
> > +	struct vm_area_struct *vma;
> > +
> > +	down_read(&current->mm->mmap_sem);
> > +	vma = find_vma_intersection(current->mm, useraddr,
> > +			useraddr + PAGE_SIZE);
> > +	if (!IS_ERR_OR_NULL(vma))
> > +		zap_page_range(vma, useraddr, PAGE_SIZE, NULL);
> > +	up_read(&current->mm->mmap_sem);
> > +}
> > +
> >  /**
> >   * splice_to_pipe - fill passed data into a pipe
> >   * @pipe:	pipe to fill
> > @@ -212,8 +224,16 @@ ssize_t splice_to_pipe(struct pipe_inode_info *pipe,
> >  			buf->len = spd->partial[page_nr].len;
> >  			buf->private = spd->partial[page_nr].private;
> >  			buf->ops = spd->ops;
> > -			if (spd->flags & SPLICE_F_GIFT)
> > +			if (spd->flags & SPLICE_F_GIFT) {
> > +				unsigned long useraddr =
> > +						spd->partial[page_nr].useraddr;
> > +
> > +				if ((spd->flags & SPLICE_F_MOVE) &&
> > +				    !buf->offset && (buf->len == PAGE_SIZE))
> > +					/* Can move page aligned buf */
> > +					zap_buf_page(useraddr);
> >  				buf->flags |= PIPE_BUF_FLAG_GIFT;
> > +			}
> 
> There isn't quite enough context here, but is it going to do this
> zap_buf_page() very often?  Seems a bit wasteful to do the up/down and
> find_vma() every trip through the loop.

The call to zap_buf_page() is in a loop where each pipe buffer is being
processed, but in that loop we have a pipe_wait() where we schedule().
So as things are structured I don't have the ability to hold mmap_sem
for multiple find_vma() calls.


  reply	other threads:[~2013-07-26 15:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 17:21 [RFC PATCH 0/2] vmpslice support for zero-copy gifting of pages Robert Jennings
2013-07-25 17:21 ` [RFC PATCH 1/2] vmsplice unmap gifted pages for recipient Robert Jennings
2013-07-25 17:30   ` Dave Hansen
2013-07-26 15:16     ` Robert Jennings [this message]
2013-07-26 16:47       ` Dave Hansen
2013-07-25 17:21 ` [RFC PATCH 2/2] Add limited zero copy to vmsplice Robert Jennings

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=20130726151621.GA5037@linux.vnet.ibm.com \
    --to=rcj@linux.vnet.ibm.com \
    --cc=aarcange@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=dave@sr71.net \
    --cc=lagarcia@linux.vnet.ibm.com \
    --cc=lilei@linux.vnet.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matt.helsley@gmail.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=riel@redhat.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).