From: Chris Mason <chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Some nilfs comments
Date: Wed, 17 Dec 2008 21:52:55 -0500 [thread overview]
Message-ID: <1229568775.27170.134.camel@think.oraclecorp.com> (raw)
Hello,
I've been meaning to read through nilfs for a while, and I grabbed the
code today to take a look. The code is very clean and it ran well out
of the box here.
One problem I hit early on was that nilfs doesn't seem to zero out the
block device during mkfs. So after mkfs.nilfs2, mount still found my
old btrfs filesystem. It would be a good idea to zero out the first and
last 1MB on the device (except for the first sector which might have the
partition table).
I haven't dug too deeply in yet, but if there are parts you're most
interested in comments on, please let me know.
It looks like nilfs_writepage ignores WB_SYNC_NONE, which is used by
do_sync_mapping_range().
nilfs_page_mkwrite doesn't seem to dirty the page? block_page_mkwrite
does more, including checks against i_size and others.
readpages and O_DIRECT both set b_size on the map_bh to reflect the
total size of the region they are trying to map. It seems like an easy
optimization to map more in nilfs_get_block.
Hopefully this helps, I'll try to send a few more ideas after I get to
know the code better.
-chris
next reply other threads:[~2008-12-18 2:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 2:52 Chris Mason [this message]
[not found] ` <1229568775.27170.134.camel-cGoWVVl3WGUrkklhUoBCrlaTQe2KTcn/@public.gmane.org>
2008-12-22 9:07 ` Some nilfs comments Ryusuke Konishi
[not found] ` <20081222.180719.88488712.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-12-22 13:01 ` Reinoud Zandijk
[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=1229568775.27170.134.camel@think.oraclecorp.com \
--to=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