Linux NILFS development
 help / color / mirror / Atom feed
From: Reinoud Zandijk <reinoud-S783fYmB3Ccdnm+yROfE0A@public.gmane.org>
To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
Cc: chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org
Subject: Re: Some nilfs comments
Date: Mon, 22 Dec 2008 14:01:52 +0100	[thread overview]
Message-ID: <20081222130152.GA23725@aardappel.13thmonkey.org> (raw)
In-Reply-To: <20081222.180719.88488712.ryusuke-sG5X7nlA6pw@public.gmane.org>

Hi Ryusuke, Chris,

On Mon, Dec 22, 2008 at 06:07:19PM +0900, Ryusuke Konishi wrote:
> Well, I feel that the following two matters are particularlly
> questionable and need to be checked:
> 
> - struct the_nilfs:
>   NILFS allows users to mount snapshots without making additional
>   devices or volumes.  This is achieved by sharing a block device
>   among multiple mount instances (i.e. super_block structs).
>   the_nilfs struct is used for this sharing.
> 
>   This approach seems to be peculiar to nilfs, and I feel it needs
>   attention.

I've dug into this too and decided to use the same mechanism for my
implementation. I think its nice to have all the fs's administration centered
at one place; i even have all the btree stuff there. One thing indeed is that
its not possible to do say `unmount /dev/wd0a' if there are multiple mounts on
it... but maybe thats better even ;) or its even a positive thing to just
unmount all the mounts in one go.

> - ioctl:
>   Ioctl interface (routines and structures) were implemented in an
>   own way.  These seems to be checked whether to comply with the rules
>   of ioctl design.

I can't comment on that yet since i haven't dug into that...

> Thanks, I've also started to read btrfs.
> I'll see it during the Christmas holidays  ;)

Whats your first impression? Want to take over things/ideas? Isn't that a
quite different FS structurally since it doesn't have segments? (AFAIK!)

With regards,
Reinoud Zandijk

  parent reply	other threads:[~2008-12-22 13:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18  2:52 Some nilfs comments Chris Mason
     [not found] ` <1229568775.27170.134.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2008-12-22  9:07   ` Ryusuke Konishi
     [not found]     ` <20081222.180719.88488712.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-12-22 13:01       ` Reinoud Zandijk [this message]
     [not found]         ` <20081222130152.GA23725-5cYspOl2ggRz6xQTk39kMVfVdRo2wo/d@public.gmane.org>
2008-12-23 17:23           ` Ryusuke Konishi
     [not found]             ` <20081224.022337.30445207.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-12-23 20:49               ` Chris Mason
2008-12-23  1:47       ` Chris Mason
     [not found]         ` <1229996820.4812.7.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2008-12-23 15:57           ` Ryusuke Konishi
2009-01-06 19:55       ` Chris Mason
     [not found]         ` <1231271709.4888.27.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2009-01-07  5:20           ` Ryusuke Konishi
     [not found]             ` <20090107.142009.106620982.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-01-07 14:16               ` Chris Mason

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=20081222130152.GA23725@aardappel.13thmonkey.org \
    --to=reinoud-s783fymb3ccdnm+yrofe0a@public.gmane.org \
    --cc=chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
    /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