linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Eric Wong <normalperson@yhbt.net>,
	linux-mm@kvack.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, Rik van Riel <riel@redhat.com>,
	Minchan Kim <minchan@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: ppoll() stuck on POLLIN while TCP peer is sending
Date: Thu, 10 Jan 2013 12:58:16 -0800	[thread overview]
Message-ID: <1357851496.27446.2619.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130110194212.GJ13304@suse.de>

On Thu, 2013-01-10 at 19:42 +0000, Mel Gorman wrote:

> Thanks Eric, it's much appreciated. However, I'm still very much in favour
> of a partial revert as in retrospect the implementation of capture took the
> wrong approach. Could you confirm the following patch works for you?
> It's should functionally have the same effect as the first revert and
> there are only minor changes from the last revert prototype I sent you
> but there is no harm in being sure.
> 
> ---8<---
> mm: compaction: Partially revert capture of suitable high-order page
> 
> Eric Wong reported on 3.7 and 3.8-rc2 that ppoll() got stuck when waiting
> for POLLIN on a local TCP socket. It was easier to trigger if there was disk
> IO and dirty pages at the same time and he bisected it to commit 1fb3f8ca
> "mm: compaction: capture a suitable high-order page immediately when it
> is made available".
> 
> The intention of that patch was to improve high-order allocations under
> memory pressure after changes made to reclaim in 3.6 drastically hurt
> THP allocations but the approach was flawed. For Eric, the problem was
> that page->pfmemalloc was not being cleared for captured pages leading to
> a poor interaction with swap-over-NFS support causing the packets to be
> dropped. However, I identified a few more problems with the patch including
> the fact that it can increase contention on zone->lock in some cases which
> could result in async direct compaction being aborted early.
> 
> In retrospect the capture patch took the wrong approach. What it should
> have done is mark the pageblock being migrated as MIGRATE_ISOLATE if it
> was allocating for THP and avoided races that way. While the patch was
> showing to improve allocation success rates at the time, the benefit is
> marginal given the relative complexity and it should be revisited from
> scratch in the context of the other reclaim-related changes that have taken
> place since the patch was first written and tested. This patch partially
> reverts commit 1fb3f8ca "mm: compaction: capture a suitable high-order
> page immediately when it is made available".
> 
> Reported-by: Eric Wong <normalperson@yhbt.net>
> Cc: stable@vger.kernel.org
> Signed-off-by: Mel Gorman <mgorman@suse.de>
> ---

It seems to solve the problem on my kvm testbed

(512 MB of ram, 2 vcpus)

Tested-by: Eric Dumazet <edumazet@google.com>


--
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>

  parent reply	other threads:[~2013-01-10 20:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121228014503.GA5017@dcvr.yhbt.net>
2013-01-02 20:08 ` Eric Wong
2013-01-02 20:47   ` Eric Wong
2013-01-03 13:41     ` Eric Dumazet
2013-01-03 18:32       ` Eric Wong
2013-01-03 23:45         ` Eric Wong
2013-01-04  0:26           ` Eric Wong
2013-01-04  3:52             ` Eric Wong
2013-01-04 16:01   ` Mel Gorman
2013-01-04 17:15     ` Eric Dumazet
2013-01-04 17:59     ` Eric Wong
2013-01-05  1:07     ` Eric Wong
2013-01-06 12:07     ` Eric Wong
2013-01-07 12:25       ` Mel Gorman
2013-01-07 22:38         ` Eric Dumazet
2013-01-08  0:21           ` Eric Wong
2013-01-07 22:38         ` Eric Wong
2013-01-08 20:14           ` Eric Wong
2013-01-08 22:43           ` Mel Gorman
2013-01-08 23:23             ` Eric Wong
2013-01-09  2:14               ` Eric Dumazet
2013-01-09  2:32                 ` Eric Dumazet
2013-01-09  2:54                   ` Eric Dumazet
2013-01-09  3:55                     ` Eric Wong
2013-01-09  8:42                       ` Eric Wong
2013-01-09  8:51                         ` Eric Wong
2013-01-09 13:42                   ` Mel Gorman
2013-01-09 13:37               ` Mel Gorman
2013-01-09 13:50                 ` Mel Gorman
2013-01-10  9:25                 ` Eric Wong
2013-01-10 19:42                   ` Mel Gorman
2013-01-10 20:03                     ` Eric Wong
2013-01-10 20:58                     ` Eric Dumazet [this message]
2013-01-11  0:51                     ` Eric Wong
2013-01-11  9:30                       ` Mel Gorman
2013-01-09 21:29             ` Eric Wong

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=1357851496.27446.2619.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=minchan@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    --cc=riel@redhat.com \
    --cc=torvalds@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox