From: Eric Dumazet <eric.dumazet@gmail.com>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Jesper Dangaard Brouer <brouer@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>, Michal Hocko <mhocko@suse.com>,
Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Linux-MM <linux-mm@kvack.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7
Date: Thu, 08 Dec 2016 08:04:10 -0800 [thread overview]
Message-ID: <1481213050.4930.102.camel@edumazet-glaptop3.roam.corp.google.com> (raw)
In-Reply-To: <20161208091806.gzcxlerxprcjvt3l@techsingularity.net>
On Thu, 2016-12-08 at 09:18 +0000, Mel Gorman wrote:
> Yes, I set it for higher speed networks as a starting point to remind me
> to examine rmem_default or socket configurations if any significant packet
> loss is observed.
Note that your page allocators changes might show more impact with
netperf and af_unix (instead of udp)
--
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>
prev parent reply other threads:[~2016-12-08 16:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 10:12 Mel Gorman
2016-12-07 14:52 ` Christoph Lameter
2016-12-07 15:57 ` Mel Gorman
2016-12-07 16:40 ` Christoph Lameter
2016-12-07 16:45 ` Mel Gorman
2016-12-07 17:11 ` Christoph Lameter
2016-12-07 17:35 ` Mel Gorman
2016-12-07 19:00 ` Eric Dumazet
2016-12-07 19:11 ` Eric Dumazet
2016-12-07 19:48 ` Mel Gorman
2016-12-07 20:10 ` Eric Dumazet
2016-12-07 21:19 ` Mel Gorman
2016-12-07 23:25 ` Mel Gorman
2016-12-08 8:22 ` Jesper Dangaard Brouer
2016-12-08 9:18 ` Mel Gorman
2016-12-08 10:43 ` Jesper Dangaard Brouer
2016-12-08 11:06 ` Mel Gorman
2016-12-08 14:48 ` Jesper Dangaard Brouer
2016-12-08 15:11 ` Mel Gorman
2016-12-08 17:19 ` Jesper Dangaard Brouer
2016-12-08 17:39 ` Mel Gorman
2016-12-08 16:04 ` Eric Dumazet [this message]
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=1481213050.4930.102.camel@edumazet-glaptop3.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brouer@redhat.com \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox