From: Christoph Hellwig <hch@infradead.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, NeilBrown <neilb@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Christoph Hellwig <hch@infradead.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH 3/6] xfs: map KM_MAYFAIL to __GFP_RETRY_MAYFAIL
Date: Tue, 27 Jun 2017 06:47:51 -0700 [thread overview]
Message-ID: <20170627134751.GA28043@infradead.org> (raw)
In-Reply-To: <20170627084950.GI28072@dhcp22.suse.cz>
On Tue, Jun 27, 2017 at 10:49:50AM +0200, Michal Hocko wrote:
> Christoph, Darrick
> could you have a look at this patch please? Andrew has put it into mmotm
> but I definitely do not want it passes your attention.
I don't think what we have to gain from it. Callsite for KM_MAYFAIL
should handler failures, but the current behavior seems to be doing fine
too.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, NeilBrown <neilb@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Christoph Hellwig <hch@infradead.org>,
"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH 3/6] xfs: map KM_MAYFAIL to __GFP_RETRY_MAYFAIL
Date: Tue, 27 Jun 2017 06:47:51 -0700 [thread overview]
Message-ID: <20170627134751.GA28043@infradead.org> (raw)
In-Reply-To: <20170627084950.GI28072@dhcp22.suse.cz>
On Tue, Jun 27, 2017 at 10:49:50AM +0200, Michal Hocko wrote:
> Christoph, Darrick
> could you have a look at this patch please? Andrew has put it into mmotm
> but I definitely do not want it passes your attention.
I don't think what we have to gain from it. Callsite for KM_MAYFAIL
should handler failures, but the current behavior seems to be doing fine
too.
next prev parent reply other threads:[~2017-06-27 13:47 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 8:53 [PATCH 0/6] mm: give __GFP_REPEAT a better semantic Michal Hocko
2017-06-23 8:53 ` Michal Hocko
2017-06-23 8:53 ` [PATCH 1/6] MIPS: do not use __GFP_REPEAT for order-0 request Michal Hocko
2017-06-23 8:53 ` Michal Hocko
2017-06-23 10:27 ` Ralf Baechle
2017-06-23 10:27 ` Ralf Baechle
2017-06-26 9:36 ` Vlastimil Babka
2017-06-26 9:36 ` Vlastimil Babka
2017-06-23 8:53 ` [PATCH 2/6] mm, tree wide: replace __GFP_REPEAT by __GFP_RETRY_MAYFAIL with more useful semantic Michal Hocko
2017-06-23 8:53 ` Michal Hocko
2017-06-26 11:45 ` Vlastimil Babka
2017-06-26 11:45 ` Vlastimil Babka
2017-06-26 12:14 ` Michal Hocko
2017-06-26 12:14 ` Michal Hocko
2017-06-26 12:17 ` Vlastimil Babka
2017-06-26 12:17 ` Vlastimil Babka
2017-06-26 12:38 ` Michal Hocko
2017-06-26 12:38 ` Michal Hocko
2017-06-26 12:42 ` Michal Hocko
2017-06-26 12:42 ` Michal Hocko
2017-06-26 11:53 ` Vlastimil Babka
2017-06-26 11:53 ` Vlastimil Babka
2017-06-23 8:53 ` [PATCH 3/6] xfs: map KM_MAYFAIL to __GFP_RETRY_MAYFAIL Michal Hocko
2017-06-23 8:53 ` Michal Hocko
2017-06-27 8:49 ` Michal Hocko
2017-06-27 8:49 ` Michal Hocko
2017-06-27 13:47 ` Christoph Hellwig [this message]
2017-06-27 13:47 ` Christoph Hellwig
2017-06-27 14:06 ` Michal Hocko
2017-06-27 14:06 ` Michal Hocko
2017-06-28 4:12 ` Darrick J. Wong
2017-06-28 4:12 ` Darrick J. Wong
2017-06-23 8:53 ` [PATCH 4/6] mm: kvmalloc support __GFP_RETRY_MAYFAIL for all sizes Michal Hocko
2017-06-23 8:53 ` Michal Hocko
2017-06-26 12:00 ` Vlastimil Babka
2017-06-26 12:00 ` Vlastimil Babka
2017-06-26 12:18 ` Michal Hocko
2017-06-26 12:18 ` Michal Hocko
2017-06-23 8:53 ` [PATCH 5/6] drm/i915: use __GFP_RETRY_MAYFAIL Michal Hocko
2017-06-23 8:53 ` Michal Hocko
2017-06-23 8:53 ` [PATCH 6/6] mm, migration: do not trigger OOM killer when migrating memory Michal Hocko
2017-06-23 8:53 ` Michal Hocko
2017-06-23 20:43 ` Andrew Morton
2017-06-23 20:43 ` Andrew Morton
2017-06-26 5:28 ` Michal Hocko
2017-06-26 5:28 ` Michal Hocko
2017-06-26 12:13 ` Vlastimil Babka
2017-06-26 12:13 ` Vlastimil Babka
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=20170627134751.GA28043@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=darrick.wong@oracle.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=neilb@suse.com \
--cc=vbabka@suse.cz \
/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.