public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] enable inode64 by default when possible
Date: Tue, 13 Apr 2010 01:35:00 -0500	[thread overview]
Message-ID: <4BC41094.7000301@hardwarefreak.com> (raw)
In-Reply-To: <20100412062158.GF2493@dastard>

Dave Chinner put forth on 4/12/2010 1:21 AM:

>> Intel Atom (32bit x86) CPUs
> 
> No, I think Atom is 64 bit.
> 
> /me checks his mailserver
> 
> Yup, it's running a 64 bit kernel and 64 bit userspace. No 32 bit
> issues there....

Nice setup Dave.  I've thought about converting my vanity server to an Atom
330 64 bit dual core microATX board.  Haven't got around to it yet.  A
little over $100 USD sent to Newegg and a bit of time is all it would take.
 With summer fast approaching I may just take the plunge to lower the heat
generation in the home office.  My current old dual proc Intel server expels
about 80-100 watts aggregate continuous at idle.  With the Atom that should
drop to well less than 30 (even more if I splurge for a new more efficient PSU).

Something maybe worthy of note:  only 5 of the 19 Atom processors are 64
bit.  The remaining 14 are 32 bit only.  Hope the link doesn't get horribly
mangled.  If it does just go to the Atom product page, click the select all
button and then compare.  That'll get you the same chart I'm looking at.

http://ark.intel.com/Compare.aspx?ids=46467,35635,35641,43517,43098,36331,41411,42503,35472,35469,41175,41176,40740,35466,41174,35463,41173,35460,40741,

I don't know how many of each Atom model have been sold, but I think it's
safe to assume there are a lot of the 32 bit only Atom CPUs in the wild.
I'll concede that probably not many such systems are running XFS, probably
just a few geeks like us.  Then again, I don't know the retail DVR market at
all, or if any units use the 32 bit Atom chips.  I would think XFS would be
a natural choice for DVR duty though.

Anyway, this may be a total non issue, but I just wanted to point out that
there are definitely some corner cases of 32 bit Atom with big XFS
filesystems in DIY DVRs/HTPCs, as well as maybe some other applications.

I'll still be 32 bit for a while on the vanity server, but my XFS
filesystems are all less than 250GB, so I'm assuming I should be safe from
inodes over 32 bits.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-04-13  6:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 19:32 [PATCH] enable inode64 by default when possible Eric Sandeen
2010-02-10 20:04 ` Emmanuel Florac
2010-02-10 20:15   ` Eric Sandeen
2010-02-10 20:42     ` Emmanuel Florac
2010-04-09 22:01 ` Alex Elder
2010-04-10  2:37   ` Stan Hoeppner
2010-04-10  3:34     ` Eric Sandeen
2010-04-12  6:21     ` Dave Chinner
2010-04-13  6:35       ` Stan Hoeppner [this message]
2010-04-14  6:57       ` Andi Kleen
2010-04-12  6:12   ` [RFC, PATCH] inode64 feature bit (was Re: [PATCH] enable inode64 by default when possible) Dave Chinner

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=4BC41094.7000301@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --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