All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <chris.mason@oracle.com>
To: Sage Weil <sage@newdream.net>
Cc: linux-btrfs@vger.kernel.org, hch@lst.de
Subject: Re: [RFC] big fat transaction ioctl
Date: Wed, 11 Nov 2009 09:54:35 -0500	[thread overview]
Message-ID: <20091111145435.GB5566@think> (raw)
In-Reply-To: <Pine.LNX.4.64.0911101143120.31818@cobra.newdream.net>

On Tue, Nov 10, 2009 at 12:12:14PM -0800, Sage Weil wrote:
> Hi all,
> 
> This is an alternative approach to atomic user transactions for btrfs.  
> The old start/end ioctls suffer from some basic limitations, namely
> 
>  - We can't properly reserve space ahead of time to avoid ENOSPC part 
> way through the transaction, and
>  - The process may die (seg fault, SIGKILL) part way through the 
> transaction.  Currently when that happens the partial transaction will 
> commit.

I like this much more than providing a journal start/stop to userland.
If we can get Christoph to ack the exports we can work on the interface
in general.

-chris

  parent reply	other threads:[~2009-11-11 14:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 20:12 [RFC] big fat transaction ioctl Sage Weil
2009-11-10 20:44 ` Andrey Kuzmin
2009-11-10 22:13   ` Sage Weil
2009-11-11  0:49     ` Jeremy Fitzhardinge
2009-11-11  5:15       ` Sage Weil
2009-11-11 15:03     ` Chris Mason
2009-11-11 15:41       ` Andrey Kuzmin
2009-11-11 15:55         ` Chris Mason
2009-11-11 17:19       ` Sage Weil
2009-11-12  3:56         ` Andrey Kuzmin
2009-11-11 14:54 ` Chris Mason [this message]
2009-11-11 18:22   ` Zach Brown
2009-11-11 22:22     ` Sage Weil

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=20091111145435.GB5566@think \
    --to=chris.mason@oracle.com \
    --cc=hch@lst.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=sage@newdream.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.