[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161208173928.gts7vsu6rqj4dicx@techsingularity.net>
Date: Thu, 8 Dec 2016 17:39:28 +0000
From: Mel Gorman <mgorman@...hsingularity.net>
To: Jesper Dangaard Brouer <brouer@...hat.com>
Cc: Eric Dumazet <eric.dumazet@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <cl@...ux.com>,
Michal Hocko <mhocko@...e.com>,
Vlastimil Babka <vbabka@...e.cz>,
Johannes Weiner <hannes@...xchg.org>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Linux-MM <linux-mm@...ck.org>,
Linux-Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7
On Thu, Dec 08, 2016 at 06:19:51PM +0100, Jesper Dangaard Brouer wrote:
> > > See patch below signature.
> > >
> > > Besides I think you misunderstood me, you can adjust:
> > > sysctl net.core.rmem_max
> > > sysctl net.core.wmem_max
> > >
> > > And you should if you plan to use/set 851968 as socket size for UDP
> > > remote tests, else you will be limited to the "max" values (212992 well
> > > actually 425984 2x default value, for reasons I cannot remember)
> > >
> >
> > The intent is to use the larger values to avoid packet loss on
> > UDP_STREAM.
>
> We do seem to misunderstand each-other.
> I was just pointing out two things:
>
> 1. Notice the difference between "max" and "default" proc setting.
> Only adjust the "max" setting.
>
> 2. There was simple BASH-shell script error in your commit.
> Patch below fix it.
>
Understood now.
> [PATCH] mmtests: actually use variable SOCKETSIZE_OPT
>
> From: Jesper Dangaard Brouer <brouer@...hat.com>
>
Applied, thanks!
--
Mel Gorman
SUSE Labs
Powered by blists - more mailing lists