All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Hugh Dickins <hughd@google.com>, Dave Jones <davej@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: shm: hang in shmem_fallocate
Date: Sun, 09 Feb 2014 20:41:54 -0500	[thread overview]
Message-ID: <52F82E62.2010709@oracle.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1402081841160.26825@eggly.anvils>

On 02/08/2014 10:25 PM, Hugh Dickins wrote:
 > Would trinity be likely to have a thread or process repeatedly faulting
 > in pages from the hole while it is being punched?

I can see how trinity would do that, but just to be certain - Cc davej.

On 02/08/2014 10:25 PM, Hugh Dickins wrote:
 > Does this happen with other holepunch filesystems?  If it does not,
 > I'd suppose it's because the tmpfs fault-in-newly-created-page path
 > is lighter than a consistent disk-based filesystem's has to be.
 > But we don't want to make the tmpfs path heavier to match them.

No, this is strictly limited to tmpfs, and AFAIK trinity tests hole
punching in other filesystems and I make sure to get a bunch of those
mounted before starting testing.


Thanks,
Sasha

WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <sasha.levin@oracle.com>
To: Hugh Dickins <hughd@google.com>, Dave Jones <davej@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: shm: hang in shmem_fallocate
Date: Sun, 09 Feb 2014 20:41:54 -0500	[thread overview]
Message-ID: <52F82E62.2010709@oracle.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1402081841160.26825@eggly.anvils>

On 02/08/2014 10:25 PM, Hugh Dickins wrote:
 > Would trinity be likely to have a thread or process repeatedly faulting
 > in pages from the hole while it is being punched?

I can see how trinity would do that, but just to be certain - Cc davej.

On 02/08/2014 10:25 PM, Hugh Dickins wrote:
 > Does this happen with other holepunch filesystems?  If it does not,
 > I'd suppose it's because the tmpfs fault-in-newly-created-page path
 > is lighter than a consistent disk-based filesystem's has to be.
 > But we don't want to make the tmpfs path heavier to match them.

No, this is strictly limited to tmpfs, and AFAIK trinity tests hole
punching in other filesystems and I make sure to get a bunch of those
mounted before starting testing.


Thanks,
Sasha

--
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-02-10  1:42 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16  4:01 mm: shm: hang in shmem_fallocate Sasha Levin
2013-12-16  4:01 ` Sasha Levin
2014-02-08 19:46 ` Sasha Levin
2014-02-08 19:46   ` Sasha Levin
2014-02-09  3:25   ` Hugh Dickins
2014-02-09  3:25     ` Hugh Dickins
2014-02-10  1:41     ` Sasha Levin [this message]
2014-02-10  1:41       ` Sasha Levin
2014-06-12 20:38       ` Sasha Levin
2014-06-12 20:38         ` Sasha Levin
2014-06-16  2:29         ` Hugh Dickins
2014-06-16  2:29           ` Hugh Dickins
2014-06-17 20:32           ` Sasha Levin
2014-06-17 20:32             ` Sasha Levin
2014-06-24 16:31           ` Vlastimil Babka
2014-06-24 16:31             ` Vlastimil Babka
2014-06-25 22:36             ` Hugh Dickins
2014-06-25 22:36               ` Hugh Dickins
2014-06-26  9:14               ` Vlastimil Babka
2014-06-26  9:14                 ` Vlastimil Babka
2014-06-26 15:19                 ` Vlastimil Babka
2014-06-26 15:19                   ` Vlastimil Babka
2014-06-27  5:36                 ` Hugh Dickins
2014-06-27  5:36                   ` Hugh Dickins
2014-07-01 11:52                   ` Vlastimil Babka
2014-07-01 11:52                     ` Vlastimil Babka
2014-07-02  1:49                     ` Hugh Dickins
2014-07-02  1:49                       ` Hugh Dickins
2014-07-09 21:59                   ` Johannes Weiner
2014-07-09 21:59                     ` Johannes Weiner
2014-07-09 22:48                     ` Hugh Dickins
2014-07-09 22:48                       ` Hugh Dickins
2014-07-10  0:51                       ` Hugh Dickins
2014-07-10  0:51                         ` Hugh Dickins
2014-06-26 15:11               ` Sasha Levin
2014-06-27  5:59                 ` Hugh Dickins
2014-06-27  5:59                   ` Hugh Dickins
2014-06-27 14:50                   ` Sasha Levin
2014-06-27 14:50                     ` Sasha Levin
2014-06-27 18:03                     ` Hugh Dickins
2014-06-27 18:03                       ` Hugh Dickins
2014-06-28 21:41                       ` Sasha Levin
2014-06-28 21:41                         ` Sasha Levin
2014-07-01 22:37                       ` mm: shmem: hang in shmem_fault (WAS: mm: shm: hang in shmem_fallocate) Sasha Levin
2014-07-01 22:37                         ` Sasha Levin
2014-07-02  0:17                         ` Hugh Dickins
2014-07-02  0:17                           ` Hugh Dickins

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=52F82E62.2010709@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=hughd@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.