From: Reinoud Zandijk <reinoud-qavaossjCcEdnm+yROfE0A@public.gmane.org>
To: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: My NiLFS2 port to NetBSD: status update
Date: Tue, 4 Jun 2013 16:02:57 +0200 [thread overview]
Message-ID: <20130604140257.GA713@diablo.13thmonkey.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
Hi Ryusuke, hi folks,
it has been some time now that i worked on my NetBSD port of NiLFS2. A
read-only version has been included in the NetBSD kernel for some two(?) years
now. I then started on creating a writing version too but it got side tracked
by various reasons like moving to a new house/home :)
I've picked up development, re-starting again, learning from earlier mistakes.
Has anything fundemental changed in the last few months? I've taken in the
changes for volume name, the 2nd superblock and such, but is there anything
more?
As for the adoption of NiLFS2 in Linux, i've seen mixed responses in reviews.
Most complain about the read/write speed. Since i dont have a reasonable test
setup and my implementation is not writing yet, how are your thoughts about
this? Is it a fundemental issue or is it more due to way its implemented?
With regards,
Reinoud
[-- Attachment #2: Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2013-06-04 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 14:02 Reinoud Zandijk [this message]
[not found] ` <20130604140257.GA713-HNv6YvNvQKMNqjISwOrxaLFspR4gePGN@public.gmane.org>
2013-06-05 0:21 ` My NiLFS2 port to NetBSD: status update Ryusuke Konishi
[not found] ` <20130605.092130.52167382.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2013-06-05 9:03 ` Reinoud Zandijk
[not found] ` <20130605090300.GA201-HNv6YvNvQKMNqjISwOrxaLFspR4gePGN@public.gmane.org>
2013-06-05 11:52 ` Vyacheslav Dubeyko
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=20130604140257.GA713@diablo.13thmonkey.org \
--to=reinoud-qavaossjccednm+yrofe0a@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@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 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.