All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Stan Hoeppner <stan@hardwarefreak.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] enable inode64 by default when possible
Date: Mon, 12 Apr 2010 16:21:58 +1000	[thread overview]
Message-ID: <20100412062158.GF2493@dastard> (raw)
In-Reply-To: <4BBFE478.3090901@hardwarefreak.com>

On Fri, Apr 09, 2010 at 09:37:44PM -0500, Stan Hoeppner wrote:
> Alex Elder put forth on 4/9/2010 5:01 PM:
> 
> > OK, it's been about two months since Eric proposed this, and
> > I'm finally getting around to writing up a response.
> > 
> > I discussed this with a few people within SGI, and there were
> > two main concerns that were mentioned:
> > - This may be a problem for some NFS clients
> > - This may be a problem for some backup software
> > We don't believe there are any direct issues with DMF or CXFS
> > in making this change.
> > 
> > I understand that the change is only in the default behavior,
> > and that forcing 32-bit inodes will still be an available
> > option.
> 
> Hi Alex,
> 
> How will this change affect those people running 32bit CPUs and kernels, if
> at all?  Or is this change related not to the word width of the hardware/OS
> but to the size of the filesystem and/or number of files/inodes contained
> within?  You mentioned possible issues with NFS.  Are there any issues with
> Samba?
> 
> 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....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  parent reply	other threads:[~2010-04-13  1:18 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 [this message]
2010-04-13  6:35       ` Stan Hoeppner
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=20100412062158.GF2493@dastard \
    --to=david@fromorbit.com \
    --cc=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 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.