All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	linux-ide <linux-ide@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
	lsf-pc@lists.linux-foundation.org
Subject: Re: [LSF/MM TOPIC] Fixing large block devices on 32 bit
Date: Fri, 31 Jan 2014 14:26:17 -0500	[thread overview]
Message-ID: <20140131192617.GA14098@redhat.com> (raw)
In-Reply-To: <1391194978.2172.20.camel@dabdike.int.hansenpartnership.com>

On Fri, Jan 31, 2014 at 11:02:58AM -0800, James Bottomley wrote:
 
 > it will only be a couple of years before 16TB devices are
 > available.  By then, I bet that most arm (and other exotic CPU) Linux
 > based personal file servers are still going to be 32 bit, so they're not
 > going to be able to take this generation (or beyond) of drives. 
 > 
 >      1. Try to pretend that CONFIG_LBDAF is supposed to cap out at 16TB
 >         and there's nothing we can do about it ... this won't be at all
 >         popular with arm based file server manufacturers.

Some of the higher end home-NAS's have already moved from arm/ppc -> x86_64[1]
Unless ARM64 starts appearing at a low enough price point, I wouldn't be 
surprised to see the smaller vendors do a similar move just to stay competitive.
(probably while keeping 'legacy' product lines for a while at a cheaper pricepoint
 that won't take bigger disks).

	Dave

[1] http://forum.synology.com/wiki/index.php/What_kind_of_CPU_does_my_NAS_have

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-01-31 19:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 19:02 [LSF/MM TOPIC] Fixing large block devices on 32 bit James Bottomley
2014-01-31 19:26 ` Dave Jones [this message]
2014-01-31 23:16   ` James Bottomley
2014-01-31 21:20 ` Chris Mason
2014-01-31 21:20   ` Chris Mason
2014-01-31 23:14   ` James Bottomley
2014-01-31 21:47 ` Dave Hansen
2014-01-31 21:47   ` Dave Hansen
2014-01-31 23:27   ` James Bottomley
2014-01-31 23:27     ` James Bottomley
2014-02-01  0:19     ` Dave Hansen
2014-02-01  0:25       ` Kirill A. Shutemov
2014-02-01  0:32         ` Dave Hansen

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=20140131192617.GA14098@redhat.com \
    --to=davej@redhat.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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.