From: Jens Axboe <jens.axboe@oracle.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: [RFC PATCH] fuse: support splice() reading from fuse device
Date: Thu, 20 May 2010 13:28:22 +0200 [thread overview]
Message-ID: <20100520112821.GP25951@kernel.dk> (raw)
In-Reply-To: <E1OF3kc-00084X-Hi@pomaz-ex.szeredi.hu>
On Thu, May 20 2010, Miklos Szeredi wrote:
> This continues zero copy I/O support on the fuse interface. The first
> part of the patchset (splice write support on fuse device) was posted
> here:
>
> http://lkml.org/lkml/2010/4/28/215
>
> With Jens' pipe growing patch and additional fuse patches it was
> possible to achieve a 20GBytes/s write throghput on my laptop in a
> "null" filesystem (no page cache, data goes to /dev/null).
Do you have some numbers on how that compares to the same test with the
default 16 page pipe size?
--
Jens Axboe
WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <jens.axboe@oracle.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org
Subject: Re: [RFC PATCH] fuse: support splice() reading from fuse device
Date: Thu, 20 May 2010 13:28:22 +0200 [thread overview]
Message-ID: <20100520112821.GP25951@kernel.dk> (raw)
In-Reply-To: <E1OF3kc-00084X-Hi@pomaz-ex.szeredi.hu>
On Thu, May 20 2010, Miklos Szeredi wrote:
> This continues zero copy I/O support on the fuse interface. The first
> part of the patchset (splice write support on fuse device) was posted
> here:
>
> http://lkml.org/lkml/2010/4/28/215
>
> With Jens' pipe growing patch and additional fuse patches it was
> possible to achieve a 20GBytes/s write throghput on my laptop in a
> "null" filesystem (no page cache, data goes to /dev/null).
Do you have some numbers on how that compares to the same test with the
default 16 page pipe size?
--
Jens Axboe
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-05-20 11:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 11:17 [RFC PATCH] fuse: support splice() reading from fuse device Miklos Szeredi
2010-05-20 11:17 ` Miklos Szeredi
2010-05-20 11:28 ` Jens Axboe [this message]
2010-05-20 11:28 ` Jens Axboe
2010-05-20 11:44 ` Miklos Szeredi
2010-05-20 11:44 ` Miklos Szeredi
2010-05-20 17:49 ` Linus Torvalds
2010-05-20 17:49 ` Linus Torvalds
2010-05-20 17:58 ` Jens Axboe
2010-05-20 17:58 ` Jens Axboe
2010-05-20 18:54 ` Miklos Szeredi
2010-05-20 18:54 ` Miklos Szeredi
2010-05-20 19:19 ` Linus Torvalds
2010-05-20 19:19 ` Linus Torvalds
2010-05-20 20:07 ` Miklos Szeredi
2010-05-20 20:07 ` Miklos Szeredi
2010-05-20 20:11 ` Matthew Wilcox
2010-05-20 20:11 ` Matthew Wilcox
2010-05-20 20:22 ` Miklos Szeredi
2010-05-20 20:22 ` Miklos Szeredi
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=20100520112821.GP25951@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miklos@szeredi.hu \
--cc=torvalds@linux-foundation.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.