Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1537647 > unrolled thread
| Started by | Mel Gorman <mgorman@techsingularity.net> |
|---|---|
| First post | 2016-12-07 11:20 +0100 |
| Last post | 2016-12-08 17:10 +0100 |
| Articles | 2 on this page of 22 — 4 participants |
Back to article view | Back to linux.kernel
[PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-07 11:20 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Christoph Lameter <cl@linux.com> - 2016-12-07 16:00 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-07 17:00 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Christoph Lameter <cl@linux.com> - 2016-12-07 17:50 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-07 17:50 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Christoph Lameter <cl@linux.com> - 2016-12-07 18:20 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-07 18:40 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Eric Dumazet <eric.dumazet@gmail.com> - 2016-12-07 20:10 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Eric Dumazet <eric.dumazet@gmail.com> - 2016-12-07 20:20 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-07 20:50 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Eric Dumazet <eric.dumazet@gmail.com> - 2016-12-07 21:20 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-07 22:30 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-08 00:30 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Jesper Dangaard Brouer <brouer@redhat.com> - 2016-12-08 09:30 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-08 10:20 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Jesper Dangaard Brouer <brouer@redhat.com> - 2016-12-08 11:50 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-08 12:10 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Jesper Dangaard Brouer <brouer@redhat.com> - 2016-12-08 15:50 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-08 16:20 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Jesper Dangaard Brouer <brouer@redhat.com> - 2016-12-08 18:30 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Mel Gorman <mgorman@techsingularity.net> - 2016-12-08 18:40 +0100
Re: [PATCH] mm: page_alloc: High-order per-cpu page allocator v7 Eric Dumazet <eric.dumazet@gmail.com> - 2016-12-08 17:10 +0100
Page 2 of 2 — ← Prev page 1 [2]
| From | Mel Gorman <mgorman@techsingularity.net> |
|---|---|
| Date | 2016-12-08 18:40 +0100 |
| Message-ID | <sMaPM-vZ-45@gated-at.bofh.it> |
| In reply to | #1538741 |
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@redhat.com> > Applied, thanks! -- Mel Gorman SUSE Labs
[toc] | [prev] | [next] | [standalone]
| From | Eric Dumazet <eric.dumazet@gmail.com> |
|---|---|
| Date | 2016-12-08 17:10 +0100 |
| Message-ID | <sM9qG-8e6-29@gated-at.bofh.it> |
| In reply to | #1538400 |
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)
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.kernel
csiph-web