From: Ben Myers <bpm@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: require 64-bit sector_t
Date: Fri, 13 Dec 2013 15:37:01 -0600 [thread overview]
Message-ID: <20131213213701.GM1935@sgi.com> (raw)
In-Reply-To: <20131114164603.GA13628@infradead.org>
Hi Christoph,
On Thu, Nov 14, 2013 at 08:46:03AM -0800, Christoph Hellwig wrote:
> Trying to support tiny disks only and saving a bit memory might have
> made sense on an SGI O2 15 years ago, but is pretty pointless today.
>
> Remove the rarely tested codepath that uses various smaller in-memory
> types to reduce our test matrix and make the codebase a little bit
> smaller and less complicated.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> diff --git a/fs/xfs/Kconfig b/fs/xfs/Kconfig
> index 399e8ce..5d47b4d 100644
> --- a/fs/xfs/Kconfig
> +++ b/fs/xfs/Kconfig
> @@ -1,6 +1,7 @@
> config XFS_FS
> tristate "XFS filesystem support"
> depends on BLOCK
> + depends on (64BIT || LBDAF)
There are quite a few 32 bit arches in use today. We need to continue to
support them in XFS as long as they are supported by the kernel. Unless I have
misunderstood what you are suggesting, I believe the answer to this patch must
be a firm 'no'.
Regards,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-13 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 16:46 [PATCH] xfs: require 64-bit sector_t Christoph Hellwig
2013-12-10 16:20 ` Christoph Hellwig
2014-06-16 14:47 ` Christoph Hellwig
2013-12-13 21:37 ` Ben Myers [this message]
2013-12-13 23:01 ` Ben Myers
2013-12-16 22:15 ` Ben Myers
2014-01-09 15:19 ` Ben Myers
2014-01-09 18:48 ` Michael L. Semon
-- strict thread matches above, loose matches on Subject: below --
2014-06-16 16:44 Christoph Hellwig
2014-06-17 14:14 ` Brian Foster
2014-06-18 15:21 ` Christoph Hellwig
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=20131213213701.GM1935@sgi.com \
--to=bpm@sgi.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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).