linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: Hans Reiser <reiser@idiom.com>,
	"Peter J. Braam" <braam@cs.cmu.edu>,
	Andrea Arcangeli <andrea@suse.de>,
	"William J. Earl" <wje@cthulhu.engr.sgi.com>,
	Tan Pong Heng <pongheng@starnet.gov.sg>,
	"Stephen C. Tweedie" <sct@redhat.com>,
	"Benjamin C.R. LaHaise" <blah@kvack.org>,
	Chris Mason <clmsys@osfmail.isc.rit.edu>,
	reiserfs@devlinux.com, linux-fsdevel@vger.rutgers.edu,
	linux-mm@kvack.org, Ingo Molnar <mingo@redhat.com>,
	Linus Torvalds <torvalds@transmeta.com>,
	intermezzo-devel@stelias.com, simmonds@stelias.com
Subject: Re: (reiserfs) Re: RFC: Re: journal ports for 2.3? (resendingbecause my
Date: Fri, 7 Jan 2000 11:37:09 +0000 (GMT)	[thread overview]
Message-ID: <14453.53221.477571.996579@dukat.scot.redhat.com> (raw)
In-Reply-To: <200001070125.UAA06650@jupiter.cs.uml.edu>

Hi,

On Thu, 6 Jan 2000 20:25:38 -0500 (EST), "Albert D. Cahalan"
<acahalan@cs.uml.edu> said:

> AIX has such an API already. It is good to clone if you can.

The AIX API is much more than a simple small-operation atomic
transaction API, isn't it?  The filesystem transactions have many
properties --- no abort, predictable size, short duration --- which make
a journaling engine inappropriate for use in a general purpose
user-visible transaction API.

--Stephen
--
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.nl.linux.org/Linux-MM/

  reply	other threads:[~2000-01-07 11:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000c01bf472c$8ad8cb60$8edb1581@isc.rit.edu>
1999-12-21  0:24 ` RFC: Re: journal ports for 2.3? Stephen C. Tweedie
1999-12-21 10:18   ` Andrea Arcangeli
1999-12-21 13:21     ` (reiserfs) " Stephen C. Tweedie
1999-12-21 13:57       ` Andrea Arcangeli
1999-12-22  0:28         ` Stephen C. Tweedie
1999-12-23 11:51           ` Hans Reiser
1999-12-22 23:37       ` Hans Reiser
2000-01-06 17:48         ` Stephen C. Tweedie
2000-01-06 18:20           ` Andrea Arcangeli
2000-01-06 21:32             ` Hans Reiser
2000-01-07 11:51               ` Stephen C. Tweedie
2000-01-07 12:46                 ` Andrea Arcangeli
2000-01-07 19:59                 ` Hans Reiser
1999-12-22  1:21     ` Benjamin C.R. LaHaise
1999-12-22 22:19       ` Stephen C. Tweedie
1999-12-22 22:41         ` (reiserfs) " Tan Pong Heng
1999-12-23  3:27           ` William J. Earl
1999-12-23 15:36             ` Andrea Arcangeli
1999-12-24  5:53               ` afei
1999-12-26  8:26               ` feiliu
2000-01-02 22:24                 ` Peter J. Braam
2000-01-05 13:02                   ` (reiserfs) Re: RFC: Re: journal ports for 2.3? (resending because my ISP probably lost it) Hans Reiser
2000-01-05 15:22                     ` Peter J. Braam
2000-01-05 15:37                       ` Tigran Aivazian
2000-01-06  8:40                         ` Hans Reiser
2000-01-05 15:50                       ` Chris Mason
2000-01-06  8:34                       ` (reiserfs) Re: RFC: Re: journal ports for 2.3? (resendingbecause " Hans Reiser
2000-01-07  1:25                         ` (reiserfs) Re: RFC: Re: journal ports for 2.3? (resendingbecause my Albert D. Cahalan
2000-01-07 11:37                           ` Stephen C. Tweedie [this message]
2000-01-06 17:54           ` (reiserfs) Re: RFC: Re: journal ports for 2.3? Stephen C. Tweedie
1999-12-23 12:02       ` Hans Reiser
1999-12-23 15:49         ` Andrea Arcangeli
1999-12-23 16:41           ` Hans Reiser
1999-12-27 16:31       ` Andrea Arcangeli

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=14453.53221.477571.996579@dukat.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=acahalan@cs.uml.edu \
    --cc=andrea@suse.de \
    --cc=blah@kvack.org \
    --cc=braam@cs.cmu.edu \
    --cc=clmsys@osfmail.isc.rit.edu \
    --cc=intermezzo-devel@stelias.com \
    --cc=linux-fsdevel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=mingo@redhat.com \
    --cc=pongheng@starnet.gov.sg \
    --cc=reiser@idiom.com \
    --cc=reiserfs@devlinux.com \
    --cc=simmonds@stelias.com \
    --cc=torvalds@transmeta.com \
    --cc=wje@cthulhu.engr.sgi.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