From: Hugh Dickins <hughd@google.com>
To: Tharindu Rukshan Bamunuarachchi <btharindu@gmail.com>
Cc: Christoph Lameter <cl@linux.com>, linux-mm@kvack.org
Subject: Re: TMPFS Maximum File Size
Date: Wed, 20 Oct 2010 09:57:44 -0700 [thread overview]
Message-ID: <AANLkTin32b4SaC0PTJpX8Pg4anQ3aSMUZFe0QFbt9y36@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikn_44WcCBmWUW=8E3q3=cznZNx=dHdOcgZSKgH@mail.gmail.com>
On Wed, Oct 20, 2010 at 6:44 AM, Tharindu Rukshan Bamunuarachchi
<btharindu@gmail.com> wrote:
>
> Is there any kind of file size limitation in TMPFS ?
There is, but it should not be affecting you. In your x86_64 case,
the tmpfs filesize limit should be slightly over 256GB.
(There's no good reason for that limit when CONFIG_SWAP is not set,
and it's then just a waste of memory on those swap vectors: I've long
wanted to #iifdef CONFIG_SWAP them, but never put in the work to do so
cleanly.)
> Our application SEGFAULT inside write() after filling 70% of TMPFS
> mount. (re-creatable but does not happen every time).
I've no idea why that should be happening: I wonder if your case is
actually triggering some memory corruption, in application or in
kernel, that manifests in that way.
But I don't quite understand what you're seeing either: a segfault in
the write() library call of your libc? an EFAULT from the kernel's
sys_write()?
Hugh
>
> We are using 98GB TMPFS without swap device. i.e. SWAP is turned off.
> Applications does not take approx. 20GB memory.
>
> we have Physical RAM of 128GB Intel x86 box running SLES 11 64bit.
> We use Infiniband, export TMPFS over NFS and IBM GPFS in same box.
> (hope those won't affect)
>
> Bit confused about "triple-indirect swap vector" ?
>
> Extracted from shmem.c ....
>
> /*
> * The maximum size of a shmem/tmpfs file is limited by the maximum size of
> * its triple-indirect swap vector - see illustration at shmem_swp_entry().
> *
> * With 4kB page size, maximum file size is just over 2TB on a 32-bit kernel,
> * but one eighth of that on a 64-bit kernel. With 8kB page size, maximum
> * file size is just over 4TB on a 64-bit kernel, but 16TB on a 32-bit kernel,
> * MAX_LFS_FILESIZE being then more restrictive than swap vector layout.
> *
>
> Thankx a lot.
> __
> Tharindu R Bamunuarachchi.
>
--
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>
next prev parent reply other threads:[~2010-10-20 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 13:44 TMPFS Maximum File Size Tharindu Rukshan Bamunuarachchi
2010-10-20 14:14 ` Christoph Lameter
2010-10-20 16:57 ` Hugh Dickins [this message]
2010-10-26 13:55 ` Tharindu Rukshan Bamunuarachchi
2010-10-27 3:44 ` Hugh Dickins
2010-10-27 20:08 ` Christoph Lameter
2010-10-28 13:35 ` Tharindu Rukshan Bamunuarachchi
2010-10-28 13:49 ` Christoph Lameter
2010-10-29 2:01 ` Tharindu Rukshan Bamunuarachchi
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=AANLkTin32b4SaC0PTJpX8Pg4anQ3aSMUZFe0QFbt9y36@mail.gmail.com \
--to=hughd@google.com \
--cc=btharindu@gmail.com \
--cc=cl@linux.com \
--cc=linux-mm@kvack.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 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).