public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Hans Reiser <reiser@namesys.com>,
	Mike Fedyk <mfedyk@matchmail.com>, Andrew Morton <akpm@osdl.org>,
	reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: precise characterization of ext3 atomicity
Date: 05 Sep 2003 09:47:20 -0400	[thread overview]
Message-ID: <1062769640.31951.209.camel@tiny.suse.com> (raw)
In-Reply-To: <20030904160344.E15623@schatzie.adilger.int>

On Thu, 2003-09-04 at 18:03, Andreas Dilger wrote:
> On Sep 05, 2003  01:32 +0400, Hans Reiser wrote:
> > Andreas Dilger wrote:
> > >It is possible to do the same with ext3, namely exporting journal_start()
> > >and journal_stop() (or some interface to them) to userspace so the application
> > >can start a transaction for multiple operations.  We had discussed this in
> > >the past, but decided not to do so because user applications can screw up in
> > >so many ways, and if an application uses these interfaces it is possible to
> > >deadlock the entire filesystem if the application isn't well behaved.
> >
> > That's why we confine it to a (finite #defined number) set of 
> > operations within one sys_reiser4 call.  At some point we will allow 
> > trusted user space processes to span multiple system calls (mail server 
> > applicances, database appliances, etc., might find this useful).  You 
> > might consider supporting sys_reiser4 at some point.

Please rename sys_reiser4 if you want it to be a generic use syscall ;-)

-chris



  reply	other threads:[~2003-09-05 13:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-04 14:20 precise characterization of ext3 atomicity Hans Reiser
2003-09-04 15:55 ` Andrew Morton
2003-09-04 15:59   ` Hans Reiser
2003-09-04 16:12     ` Andrew Morton
2003-09-04 16:25       ` Hans Reiser
2003-09-04 18:15         ` Mike Fedyk
2003-09-04 16:05           ` Antonio Vargas
2003-09-04 18:37           ` Hans Reiser
2003-09-04 19:12             ` Mike Fedyk
2003-09-04 21:03               ` Hans Reiser
2003-09-04 19:28             ` Andreas Dilger
2003-09-04 21:32               ` Hans Reiser
2003-09-04 22:03                 ` Andreas Dilger
2003-09-05 13:47                   ` Chris Mason [this message]
2003-09-09 13:09                 ` Pavel Machek
2003-09-09 19:21                   ` Gábor Lénárt
2003-09-09 19:43                     ` Mike Fedyk
2003-09-04 20:16   ` Daniel Phillips
2003-09-04 20:10     ` Andrew Morton
2003-09-04 21:08       ` Daniel Phillips
2003-09-04 21:39         ` Hans Reiser
2003-09-04 21:59           ` Daniel Phillips

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=1062769640.31951.209.camel@tiny.suse.com \
    --to=mason@suse.com \
    --cc=adilger@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    /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