All of lore.kernel.org
 help / color / mirror / Atom feed
From: <system_lists@nullzone.org>
To: 'Reiserfs List' <reiserfs-list@namesys.com>
Subject: RE: reiser4 data journalling?
Date: Fri, 29 Aug 2003 23:56:23 +0200	[thread overview]
Message-ID: <008201c36e78$63425bd0$0202a8c0@main> (raw)
In-Reply-To: <3F4FC8FD.1050303@namesys.com>


> -----Mensaje original-----
> De: Hans Reiser [mailto:reiser@namesys.com]
> Enviado el: viernes, 29 de agosto de 2003 23:43
> Para: Nikita Danilov
> CC: Oleg Drokin; Mike Fedyk; Tom Vier; Reiserfs List
> Asunto: Re: reiser4 data journalling?
> 
> Nikita Danilov wrote:
> 
> >Hans Reiser writes:
> > > Oleg Drokin wrote:
> > >
> > > >Hello!
> > > >
> > > >On Thu, Aug 28, 2003 at 06:23:22PM -0700, Mike Fedyk wrote:
> > > >
> > > >
> > > >
> > > >>So you can have one 5k memory area that spans two pages, and it will
> act on
> > > >>them atomically?  Or does that mean that the utils are already page
> aligned
> > > >>by other kernel mechanisims?  Or that they'll have to use the reiser
> API to
> > > >>do some of the above (other than the op grouping)?
> > > >>
> > > >>
> > > >
> > > >Data does not need to be page aligned for atomic operations.
> > > >
> > > >Bye,
> > > >    Oleg
> > > >
> > > >
> > > >
> > > >
> > > in reiser4
> >
> >Why?
> >
> >
> >
> Because atomicity in ext3 basically consists of guaranteeing that the
> filesystem is consistent, and due to the disk drive implementation 4k
> blocks are written atomically.  So, if you span more than one block, it is
> not guaranteed to be atomic.
> 
> Someone should correct me if I got it wrong, as ext3 is not my
> specialty....
> 

I think that is right.



  reply	other threads:[~2003-08-29 21:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 17:25 reiser4 data journalling? Tupshin Harper
2003-08-28 17:42 ` Nikita Danilov
2003-08-28 20:48   ` Hans Reiser
2003-08-29  0:18     ` Tom Vier
2003-08-29  0:21       ` Hans Reiser
2003-08-29  1:23         ` Mike Fedyk
2003-08-29  5:08           ` Oleg Drokin
2003-08-29 17:48             ` Hans Reiser
2003-08-29 18:15               ` Nikita Danilov
2003-08-29 18:17                 ` Nikita Danilov
2003-08-29 21:43                 ` Hans Reiser
2003-08-29 21:56                   ` system_lists [this message]
2003-08-30 18:22                   ` Andi Kleen
2003-09-02 22:21                     ` Hans Reiser
2003-09-03  2:05                       ` Tom Vier
2003-08-29 21:47           ` Hans Reiser
2003-08-29 13:12       ` Lars Marowsky-Bree
2003-09-02 22:17         ` Hans Reiser
2003-09-03 10:52           ` Lars Marowsky-Bree
2003-09-03 16:56             ` Hans Reiser

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='008201c36e78$63425bd0$0202a8c0@main' \
    --to=system_lists@nullzone.org \
    --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 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.