public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Maxim Patlasov <mpatlasov@parallels.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"fuse-devel@lists.sourceforge.net"
	<fuse-devel@lists.sourceforge.net>
Subject: Re: [PATCH 0/3] fuse: fixes for writepages
Date: Fri, 20 Sep 2013 12:06:10 +0400	[thread overview]
Message-ID: <523C01F2.40006@parallels.com> (raw)
In-Reply-To: <1379607116-13382-1-git-send-email-miklos@szeredi.hu>

Miklos,

On 09/19/2013 08:11 PM, Miklos Szeredi wrote:
> Maxim,
>
> Please review and test these.  I've appended them to writepages.v2 and for-next.

Thanks a lot for efforts. I'll start to work on it now and send you 
feedback as soon as I get a progress.

Btw, adding fuse-devel to cc.

Thanks,
Maxim

>
> Here's a test patch for the rewrites stuff.  It simply disables the waiting in
> fuse_page_mkwrite() and is quite effective in generating rewrites in my
> testcase.
>
> Thanks,
> Miklos
>
> ---
>   fs/fuse/file.c |    6 +++++-
>   1 file changed, 5 insertions(+), 1 deletion(-)
>
> --- a/fs/fuse/file.c
> +++ b/fs/fuse/file.c
> @@ -1498,6 +1498,7 @@ static void fuse_writepage_end(struct fu
>   
>   	mapping_set_error(inode->i_mapping, req->out.h.error);
>   	spin_lock(&fc->lock);
> +	int count = 0;
>   	while (req->misc.write.next) {
>   		struct fuse_req *next = req->misc.write.next;
>   		req->misc.write.next = next->misc.write.next;
> @@ -1505,7 +1506,10 @@ static void fuse_writepage_end(struct fu
>   		list_add(&next->writepages_entry, &fi->writepages);
>   		list_add_tail(&next->list, &fi->queued_writes);
>   		fuse_flush_writepages(inode);
> +		count++;
>   	}
> +	if (count)
> +		printk("rewrite: %i\n", count);
>   	fi->writectr--;
>   	fuse_writepage_finish(fc, req);
>   	spin_unlock(&fc->lock);
> @@ -1884,7 +1888,7 @@ static int fuse_page_mkwrite(struct vm_a
>   		return VM_FAULT_NOPAGE;
>   	}
>   
> -	fuse_wait_on_page_writeback(inode, page->index);
> +	//fuse_wait_on_page_writeback(inode, page->index);
>   	return VM_FAULT_LOCKED;
>   }
>   
>
>
>


      parent reply	other threads:[~2013-09-20  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 16:11 [PATCH 0/3] fuse: fixes for writepages Miklos Szeredi
2013-09-19 16:11 ` [PATCH 1/3] fuse: writepages: fix aggregation Miklos Szeredi
2013-09-19 16:11 ` [PATCH 2/3] fuse: writepages: handle same page rewrites Miklos Szeredi
2013-09-19 16:11 ` [PATCH 3/3] fuse: writepage: skip already in flight Miklos Szeredi
2013-09-20  8:06 ` Maxim Patlasov [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=523C01F2.40006@parallels.com \
    --to=mpatlasov@parallels.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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