From: Vyacheslav Dubeyko <slava-yeENwD64cLxBDgjK7y7TUQ@public.gmane.org>
To: Ryusuke Konishi
<konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Clemens Eisserer
<linuxhippy-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH v2] nilfs2: implement calculation of free inodes count
Date: Tue, 14 May 2013 10:50:54 +0400 [thread overview]
Message-ID: <1368514254.2739.9.camel@slavad-ubuntu> (raw)
In-Reply-To: <20130514.031840.27794271.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
Hi Ryusuke,
On Tue, 2013-05-14 at 03:18 +0900, Ryusuke Konishi wrote:
[snip]
>
> > /**
> > + * nilfs_palloc_count_max_entries - count max number of entries that can be
> > + * described by @desc_blocks
> > + * @inode: inode of metadata file using this allocator
> > + * @desc_blocks: descriptor blocks count
> > + */
> > +u64 nilfs_palloc_count_max_entries(struct inode *inode,
> > + unsigned int desc_blocks)
>
> The logical upper limit of descriptor block count is 2 ^ 43 (in the
> case of 64-bit architecture), so the desc_blocks argument should have
> unsigned long type.
>
I think that in real world the int type will be enough for descriptor
blocks count. Moreover, I use atomic_t type for storing knowledge about
current known descriptor blocks count in nilfs_mdt_info structure. If
you insist on using unsigned long type then atomic_t type is not good
choice. But do you really think that we have to use the unsigned long
type for descriptor blocks count?
With the best regards,
Vyacheslav Dubeyko.
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-05-14 6:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 11:54 [PATCH v2] nilfs2: implement calculation of free inodes count Vyacheslav Dubeyko
2013-05-13 18:18 ` Ryusuke Konishi
[not found] ` <20130514.031840.27794271.konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org>
2013-05-14 6:50 ` Vyacheslav Dubeyko [this message]
2013-05-15 2:56 ` Ryusuke Konishi
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=1368514254.2739.9.camel@slavad-ubuntu \
--to=slava-yeenwd64clxbdgjk7y7tuq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=konishi.ryusuke-Zyj7fXuS5i5L9jVzuh4AOg@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxhippy-Re5JQEeQqe8AvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).