From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Alex Lyakas <alex.bolshoy.btrfs@gmail.com>,
Jan Schmidt <list.btrfs@jan-o-sch.net>,
Alexander Block <ablock84@googlemail.com>
Subject: Re: btrfs send/receive review by vfs folks
Date: Sat, 6 Oct 2012 11:40:26 +0200 [thread overview]
Message-ID: <201210061140.26936.Martin@lichtvoll.de> (raw)
In-Reply-To: <CAHf9xvY1TSNa-zY82whUrK6DtnFYiNx1BEF6R1kGQj1HU+wbxA@mail.gmail.com>
Am Donnerstag, 4. Oktober 2012 schrieb Alex Lyakas:
> Hi Jan,
> as I promised, here is some code for you to look at.
>
> First I will describe the approach in general.
>
> # Get rid of the pipe. Instead, user-space passes a buffer and kernel
> fills the specified user-space buffer with commands.
> # When the buffer is full, kernel stops generating commands and
> returns a checkpoint to the user-space.
Can it just fill a second buffer while userspace command handles the first?
> # User-space does whatever it wants with the returned buffer, and then
> calls the kernel again, with a buffer and a checkpoint that was
> returned by the kernel from previous SEND ioctl().
> # Kernel re-arms itself to the specified checkpoint, and fills the
> specified buffer with commands, attaches a new checkpoint and so on.
> # Eventually kernel signals to the user that there are no more
> commands.
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
next prev parent reply other threads:[~2012-10-06 9:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 12:09 btrfs send/receive review by vfs folks Alexander Block
2012-09-24 9:13 ` Alex Lyakas
2012-09-24 9:27 ` Jan Schmidt
2012-09-27 19:36 ` Alex Lyakas
2012-10-04 15:59 ` Alex Lyakas
2012-10-06 9:40 ` Martin Steigerwald [this message]
2012-10-07 10:48 ` Alex Lyakas
2012-10-07 10:53 ` Martin Steigerwald
2012-10-07 11:08 ` Alex Lyakas
2012-10-07 12:59 ` Martin Steigerwald
2012-10-08 9:26 ` Jan Schmidt
2012-10-08 11:38 ` Alex Lyakas
2012-10-08 13:37 ` Jan Schmidt
2012-10-10 20:28 ` Alex Lyakas
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=201210061140.26936.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=ablock84@googlemail.com \
--cc=alex.bolshoy.btrfs@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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.