From: Christoph Hellwig <hch@infradead.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Viacheslav Dubeyko <slava@dubeyko.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Vyacheslav.Dubeyko@hgst.com, Cyril.Guyot@hgst.com,
Adam.Manzanares@hgst.com, Damien.LeMoal@hgst.com
Subject: Re: [PATCH] f2fs: introduce on-disk layout version checking functionality
Date: Tue, 24 May 2016 01:53:43 -0700 [thread overview]
Message-ID: <20160524085343.GC8121@infradead.org> (raw)
In-Reply-To: <20160523211357.GA17297@jaegeuk.gateway>
On Mon, May 23, 2016 at 02:13:57PM -0700, Jaegeuk Kim wrote:
> As Christoph mentioned, how about checking the feature only like this?
>
> 1. if the feature is ON,
> - go 64 bits , when compiled w/ F2FS_MIN_16TB_VOLUME_SUPPORT
> - fail to mount, when compiled w/o F2FS_MIN_16TB_VOLUME_SUPPORT
>
> 2. if the feature is OFF,
> - fail to mount, when compiled w/ F2FS_MIN_16TB_VOLUME_SUPPORT
> - go 32 bits , when compiled w/o F2FS_MIN_16TB_VOLUME_SUPPORT
>
> Thoughts?
That goes on to the next question: why do we even need a config option
for 16TB+ volume support?
next prev parent reply other threads:[~2016-05-24 8:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 17:46 [PATCH] f2fs: introduce on-disk layout version checking functionality Viacheslav Dubeyko
2016-05-20 7:58 ` Christoph Hellwig
2016-05-20 18:30 ` Viacheslav Dubeyko
2016-05-23 8:25 ` Christoph Hellwig
2016-05-23 20:08 ` Viacheslav Dubeyko
2016-05-24 8:52 ` Christoph Hellwig
2016-05-25 0:53 ` Viacheslav Dubeyko
2016-05-23 21:13 ` Jaegeuk Kim
2016-05-24 8:53 ` Christoph Hellwig [this message]
2016-05-25 0:34 ` Viacheslav Dubeyko
2016-05-25 1:05 ` Viacheslav Dubeyko
2016-05-25 17:12 ` Jaegeuk Kim
2016-05-25 17:46 ` Viacheslav 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=20160524085343.GC8121@infradead.org \
--to=hch@infradead.org \
--cc=Adam.Manzanares@hgst.com \
--cc=Cyril.Guyot@hgst.com \
--cc=Damien.LeMoal@hgst.com \
--cc=Vyacheslav.Dubeyko@hgst.com \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.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 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).