Re: [PATCH v4 09/29] fork: Add generic vmalloced stack support

On Fri, Jul 1, 2016 at 7:59 AM, Borislav Petkov wrote: > On Sun, Jun 26, 2016 at 02:55:31PM -0700, Andy Lutomirski wrote: >> If CONFIG_VMAP_STACK is selected, kernel stacks are allocated with >> vmalloc_node. >> All done.

Re: [PATCH 1/6] x86: fix duplicated X86_BUG(9) macro

On Jul 1, 2016 2:23 AM, "Borislav Petkov" wrote: > > On Thu, Jun 30, 2016 at 05:12:10PM -0700, Dave Hansen wrote: > > > > From: Dave Hansen > > > > epufeatures.h currently defines X86_BUG(9) twice on 32-bit: > > > > #define X86_BUG_NULL_SEG

Re: [PATCH v4 09/29] fork: Add generic vmalloced stack support

On Fri, Jul 1, 2016 at 7:59 AM, Borislav Petkov wrote: > On Sun, Jun 26, 2016 at 02:55:31PM -0700, Andy Lutomirski wrote: >> If CONFIG_VMAP_STACK is selected, kernel stacks are allocated with >> vmalloc_node. >> All done.

Re: [PATCH 1/6] x86: fix duplicated X86_BUG(9) macro

On Jul 1, 2016 2:23 AM, "Borislav Petkov" wrote: > > On Thu, Jun 30, 2016 at 05:12:10PM -0700, Dave Hansen wrote: > > > > From: Dave Hansen > > > > epufeatures.h currently defines X86_BUG(9) twice on 32-bit: > > > > #define X86_BUG_NULL_SEGX86_BUG(9) /* Nulling a selector > >

Re: [PATCH v003] Added support for gcc version >= 6

On Fri, 2016-07-01 at 15:09 +0200, Florian Meier wrote: > Added support for gcc version >= 6 in gcov. It's important to mention the subsystem in the patch subject e.g. "Subject: [PATCH V3] gcov: Support gcc version >= 6"

Re: [PATCH v003] Added support for gcc version >= 6

On Fri, 2016-07-01 at 15:09 +0200, Florian Meier wrote: > Added support for gcc version >= 6 in gcov. It's important to mention the subsystem in the patch subject e.g. "Subject: [PATCH V3] gcov: Support gcc version >= 6"

Re: [PATCH 6/6] x86: Fix stray A/D bit setting into non-present PTEs

On Fri, Jul 1, 2016 at 9:14 AM, Dave Hansen wrote: > > As I understand it, the erratum only affects a thread which is about to > page fault. The write associated with the dirty bit being set never > actually gets executed. So, the bit really *is* stray and isn't > something we

Re: [PATCH 6/6] x86: Fix stray A/D bit setting into non-present PTEs

On Fri, Jul 1, 2016 at 9:14 AM, Dave Hansen wrote: > > As I understand it, the erratum only affects a thread which is about to > page fault. The write associated with the dirty bit being set never > actually gets executed. So, the bit really *is* stray and isn't > something we need to preserve.

Re: [PATCH v2 3/3] drivers core: allow id match override when manually binding driver

On Fri, Jul 01, 2016 at 05:37:53PM +0200, Michal Suchanek wrote: > Can you, please, specify what problems this patch creates for other users > and maintainability? To repeat yet again a major design goal for DT is to describe the hardware rather than implementation details of the software you

Re: mfd: dm355evm_msp: Refactoring for add_child()

On Fri, 2016-07-01 at 16:40 +0200, SF Markus Elfring wrote: > > > > Can you please fix your email client to _not_ send References: > > and In-reply-to: headers when sending new patches? > I prefer to associate some patches with previous relevant > discussion directly. > > > > > > Even better

Re: [PATCH v2 3/3] drivers core: allow id match override when manually binding driver

On Fri, Jul 01, 2016 at 05:37:53PM +0200, Michal Suchanek wrote: > Can you, please, specify what problems this patch creates for other users > and maintainability? To repeat yet again a major design goal for DT is to describe the hardware rather than implementation details of the software you

Re: mfd: dm355evm_msp: Refactoring for add_child()

On Fri, 2016-07-01 at 16:40 +0200, SF Markus Elfring wrote: > > > > Can you please fix your email client to _not_ send References: > > and In-reply-to: headers when sending new patches? > I prefer to associate some patches with previous relevant > discussion directly. > > > > > > Even better

Re: A potential race

On 07/01/2016 05:02 PM, Pavel Andrianov wrote: > 01.07.2016 19:53, Hans Verkuil пишет: >> On 07/01/2016 04:39 PM, Pavel Andrianov wrote: >>> Hi! >>> >>> There is a potential race condition between usbvision_v4l2_close and >>> usbvision_disconnect. The possible scenario may be the following.

Re: A potential race

On 07/01/2016 05:02 PM, Pavel Andrianov wrote: > 01.07.2016 19:53, Hans Verkuil пишет: >> On 07/01/2016 04:39 PM, Pavel Andrianov wrote: >>> Hi! >>> >>> There is a potential race condition between usbvision_v4l2_close and >>> usbvision_disconnect. The possible scenario may be the following.

[GIT PULL] Staging/IIO driver fixes for 4.7-rc6

The following changes since commit 33688abb2802ff3a230bd2441f765477b94cc89e: Linux 4.7-rc4 (2016-06-19 21:30:02 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.7-rc6 for you to fetch changes up to

[GIT PULL] Staging/IIO driver fixes for 4.7-rc6

The following changes since commit 33688abb2802ff3a230bd2441f765477b94cc89e: Linux 4.7-rc4 (2016-06-19 21:30:02 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git/ tags/staging-4.7-rc6 for you to fetch changes up to

[GIT PULL] TTY fixes for 4.7-rc6

The following changes since commit 33688abb2802ff3a230bd2441f765477b94cc89e: Linux 4.7-rc4 (2016-06-19 21:30:02 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-4.7-rc6 for you to fetch changes up to

[GIT PULL] TTY fixes for 4.7-rc6

The following changes since commit 33688abb2802ff3a230bd2441f765477b94cc89e: Linux 4.7-rc4 (2016-06-19 21:30:02 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/ tags/tty-4.7-rc6 for you to fetch changes up to

[GIT PULL] USB driver fixes for 4.7-rc6

The following changes since commit 33688abb2802ff3a230bd2441f765477b94cc89e: Linux 4.7-rc4 (2016-06-19 21:30:02 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.7-rc6 for you to fetch changes up to

Re: [PATCH 6/6] x86: Fix stray A/D bit setting into non-present PTEs

On 07/01/2016 09:07 AM, Linus Torvalds wrote: > But I also started worrying about us just losing sight of the dirty > bit in particular. It's not enough that we ignore the dirty bit - we'd > still want to make sure that the underlying backing page gets marked > dirty, even if the CPU is buggy and

[GIT PULL] USB driver fixes for 4.7-rc6

The following changes since commit 33688abb2802ff3a230bd2441f765477b94cc89e: Linux 4.7-rc4 (2016-06-19 21:30:02 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/ tags/usb-4.7-rc6 for you to fetch changes up to

Re: [PATCH 6/6] x86: Fix stray A/D bit setting into non-present PTEs

On 07/01/2016 09:07 AM, Linus Torvalds wrote: > But I also started worrying about us just losing sight of the dirty > bit in particular. It's not enough that we ignore the dirty bit - we'd > still want to make sure that the underlying backing page gets marked > dirty, even if the CPU is buggy and

Re: [alsa-devel] [PATCH v5 7/9] ASoC: bt-sco: extend rate and add a general compatible string

On Fri, Jul 01, 2016 at 10:49:46AM +0800, Garlic Tseng wrote: > On Thu, 2016-06-30 at 20:55 +0800, Garlic Tseng wrote: > > If you worry about some potential risk (I don't see any) maybe we have > > to develop another dummy bt-sco codec driver which support both 8k and > > 16k? > Ah! If someone

Re: [alsa-devel] [PATCH v5 7/9] ASoC: bt-sco: extend rate and add a general compatible string

On Fri, Jul 01, 2016 at 10:49:46AM +0800, Garlic Tseng wrote: > On Thu, 2016-06-30 at 20:55 +0800, Garlic Tseng wrote: > > If you worry about some potential risk (I don't see any) maybe we have > > to develop another dummy bt-sco codec driver which support both 8k and > > 16k? > Ah! If someone

Re: mm: BUG in page_move_anon_rmap

On Fri, Jul 1, 2016 at 6:03 PM, Andrey Ryabinin wrote: > > > On 07/01/2016 06:31 PM, Dmitry Vyukov wrote: >> Hello, >> >> I am getting the following crashes while running syzkaller fuzzer on >> 00bf377d19ad3d80cbc7a036521279a86e397bfb (Jun 29). So far I did not >> manage

Re: mm: BUG in page_move_anon_rmap

On Fri, Jul 1, 2016 at 6:03 PM, Andrey Ryabinin wrote: > > > On 07/01/2016 06:31 PM, Dmitry Vyukov wrote: >> Hello, >> >> I am getting the following crashes while running syzkaller fuzzer on >> 00bf377d19ad3d80cbc7a036521279a86e397bfb (Jun 29). So far I did not >> manage to reproduce it outside

Re: [PATCH v2] PM / suspend: show workqueue state in suspend flow

On Fri, Jul 01, 2016 at 11:05:02AM +0800, Roger Lu wrote: > If freezable workqueue aborts suspend flow, show > workqueue state for debug purpose. > > Signed-off-by: Roger Lu Acked-by: Tejun Heo Rafael, can you please pick this on up? Thanks. -- tejun

Re: [PATCH v2] PM / suspend: show workqueue state in suspend flow

On Fri, Jul 01, 2016 at 11:05:02AM +0800, Roger Lu wrote: > If freezable workqueue aborts suspend flow, show > workqueue state for debug purpose. > > Signed-off-by: Roger Lu Acked-by: Tejun Heo Rafael, can you please pick this on up? Thanks. -- tejun

Re: [PATCH 6/6] x86: Fix stray A/D bit setting into non-present PTEs

On Thu, Jun 30, 2016 at 9:39 PM, Dave Hansen wrote: > > I think what you suggest will work if we don't consider A/D in > pte_none(). I think there are a bunch of code path where assume that > !pte_present() && !pte_none() means swap. Hmm. Thinking about it some more, I still

Re: [PATCH 6/6] x86: Fix stray A/D bit setting into non-present PTEs

On Thu, Jun 30, 2016 at 9:39 PM, Dave Hansen wrote: > > I think what you suggest will work if we don't consider A/D in > pte_none(). I think there are a bunch of code path where assume that > !pte_present() && !pte_none() means swap. Hmm. Thinking about it some more, I still think it's a good

Re: strange Mac OSX RST behavior

> On Mac OSX 10.11.5 (latest version), we have found that when tcp > connections are abruptly terminated (via ^C), a FIN is sent followed > by an RST packet. The RST is sent with the same sequence number as the > FIN, and thus dropped since the stack only accepts RST packets matching > rcv_nxt

Re: strange Mac OSX RST behavior

> On Mac OSX 10.11.5 (latest version), we have found that when tcp > connections are abruptly terminated (via ^C), a FIN is sent followed > by an RST packet. The RST is sent with the same sequence number as the > FIN, and thus dropped since the stack only accepts RST packets matching > rcv_nxt

Re: A potential race

01.07.2016 19:53, Hans Verkuil пишет: On 07/01/2016 04:39 PM, Pavel Andrianov wrote: Hi! There is a potential race condition between usbvision_v4l2_close and usbvision_disconnect. The possible scenario may be the following. usbvision_disconnect starts execution, assigns

Re: A potential race

01.07.2016 19:53, Hans Verkuil пишет: On 07/01/2016 04:39 PM, Pavel Andrianov wrote: Hi! There is a potential race condition between usbvision_v4l2_close and usbvision_disconnect. The possible scenario may be the following. usbvision_disconnect starts execution, assigns

Re: mm: BUG in page_move_anon_rmap

On 07/01/2016 06:31 PM, Dmitry Vyukov wrote: > Hello, > > I am getting the following crashes while running syzkaller fuzzer on > 00bf377d19ad3d80cbc7a036521279a86e397bfb (Jun 29). So far I did not > manage to reproduce it outside of fuzzer, but fuzzer hits it once per > hour or so. > > flags:

Re: mm: BUG in page_move_anon_rmap

On 07/01/2016 06:31 PM, Dmitry Vyukov wrote: > Hello, > > I am getting the following crashes while running syzkaller fuzzer on > 00bf377d19ad3d80cbc7a036521279a86e397bfb (Jun 29). So far I did not > manage to reproduce it outside of fuzzer, but fuzzer hits it once per > hour or so. > > flags:

Re: [PATCH v1 06/11] KVM: x86: use hardware-compatible format for APIC ID register

2016-07-01 17:07+0200, Paolo Bonzini: > On 01/07/2016 16:54, Radim Krčmář wrote: >>> >(Hint: we >>> > want kvm-unit-tests for this). >> :) Something like this? >> >> enable_xapic() >> id = apic_id() >> set_apic_id(id+1) // ? >>

Re: [PATCH v1 06/11] KVM: x86: use hardware-compatible format for APIC ID register

2016-07-01 17:07+0200, Paolo Bonzini: > On 01/07/2016 16:54, Radim Krčmář wrote: >>> >(Hint: we >>> > want kvm-unit-tests for this). >> :) Something like this? >> >> enable_xapic() >> id = apic_id() >> set_apic_id(id+1) // ? >>

[PATCH] pinctrl: qcom: add support for EBI2

Add support to mux in the second external bus interface as function 1 on pins 123 thru 158. This external bus is used on the APQ8060 Dragonboard to connect an external SMSC9211 ethernet adapter. Cc: Stephen Boyd Cc: Bjorn Andersson

Re: A potential race

On 07/01/2016 04:39 PM, Pavel Andrianov wrote: > Hi! > > There is a potential race condition between usbvision_v4l2_close > > and usbvision_disconnect >

[PATCH] pinctrl: qcom: add support for EBI2

Add support to mux in the second external bus interface as function 1 on pins 123 thru 158. This external bus is used on the APQ8060 Dragonboard to connect an external SMSC9211 ethernet adapter. Cc: Stephen Boyd Cc: Bjorn Andersson Signed-off-by: Linus Walleij ---

Re: A potential race

On 07/01/2016 04:39 PM, Pavel Andrianov wrote: > Hi! > > There is a potential race condition between usbvision_v4l2_close > > and usbvision_disconnect >

Re: [PATCH v1 03/11] KVM: x86: dynamic kvm_apic_map

2016-07-01 17:12+0200, Paolo Bonzini: > On 01/07/2016 17:06, Paolo Bonzini wrote: >> > Should it? >>> Yes, x2APIC ID cannot be changed in hardware and is initialized to the >>> intitial APIC ID. >>> Letting LAPIC_SET change x2APIC ID would allow scenarios where userspace >>> reuses old VMs

Re: [PATCH 6/6] x86: Fix stray A/D bit setting into non-present PTEs

On 07/01/2016 07:25 AM, Eric W. Biederman wrote: > Linus Torvalds writes: >> > On Thu, Jun 30, 2016 at 9:39 PM, Dave Hansen wrote: >>> >> >>> >> I think what you suggest will work if we don't consider A/D in >>> >> pte_none(). I think there are a

Re: [PATCH v1 03/11] KVM: x86: dynamic kvm_apic_map

2016-07-01 17:12+0200, Paolo Bonzini: > On 01/07/2016 17:06, Paolo Bonzini wrote: >> > Should it? >>> Yes, x2APIC ID cannot be changed in hardware and is initialized to the >>> intitial APIC ID. >>> Letting LAPIC_SET change x2APIC ID would allow scenarios where userspace >>> reuses old VMs

Re: [PATCH 6/6] x86: Fix stray A/D bit setting into non-present PTEs

On 07/01/2016 07:25 AM, Eric W. Biederman wrote: > Linus Torvalds writes: >> > On Thu, Jun 30, 2016 at 9:39 PM, Dave Hansen wrote: >>> >> >>> >> I think what you suggest will work if we don't consider A/D in >>> >> pte_none(). I think there are a bunch of code path where assume that >>> >>

Re: [RFC] arm64: kexec_file_load support

Am Freitag, 01 Juli 2016, 14:11:12 schrieb AKASHI Takahiro: > I'm not sure whether there is any demand for kexec_file_load > support on arm64, but anyhow I'm working on this and now > my early prototype code does work fine. It is necessary if you want to support loading only signed kernels, and

Re: [PATCH v003] Added support for gcc version >= 6

On 01.07.2016 15:09, Florian Meier wrote: > Added support for gcc version >= 6 in gcov. > > Signed-off-by: Florian Meier Looks good, thanks! Tested successfully with gcc 4.8.5 and gcc 6.1.0. Andrew, could you pick this change up via your tree?

[PATCH 03/31] mm, vmscan: move LRU lists to node

This moves the LRU lists from the zone to the node and related data such as counters, tracing, congestion tracking and writeback tracking. Unfortunately, due to reclaim and compaction retry logic, it is necessary to account for the number of LRU pages on both zone and node logic. Most reclaim

Re: [RFC] arm64: kexec_file_load support

Am Freitag, 01 Juli 2016, 14:11:12 schrieb AKASHI Takahiro: > I'm not sure whether there is any demand for kexec_file_load > support on arm64, but anyhow I'm working on this and now > my early prototype code does work fine. It is necessary if you want to support loading only signed kernels, and

Re: [PATCH v003] Added support for gcc version >= 6

On 01.07.2016 15:09, Florian Meier wrote: > Added support for gcc version >= 6 in gcov. > > Signed-off-by: Florian Meier Looks good, thanks! Tested successfully with gcc 4.8.5 and gcc 6.1.0. Andrew, could you pick this change up via your tree? Reviewed-by: Peter Oberparleiter Tested-by: Peter

[PATCH 03/31] mm, vmscan: move LRU lists to node

This moves the LRU lists from the zone to the node and related data such as counters, tracing, congestion tracking and writeback tracking. Unfortunately, due to reclaim and compaction retry logic, it is necessary to account for the number of LRU pages on both zone and node logic. Most reclaim

Re: [PATCH v3 1/4] drm/rockchip: vop: export line flag function

On Fri, Jul 1, 2016 at 11:30 AM, Sean Paul wrote: > On Fri, Jul 1, 2016 at 5:19 AM, Yakir Yang wrote: >> VOP have integrated a hardware counter which indicate the exact display >> line that vop is scanning. And if we're interested in a specific line,

Re: [PATCH v3 1/4] drm/rockchip: vop: export line flag function

On Fri, Jul 1, 2016 at 11:30 AM, Sean Paul wrote: > On Fri, Jul 1, 2016 at 5:19 AM, Yakir Yang wrote: >> VOP have integrated a hardware counter which indicate the exact display >> line that vop is scanning. And if we're interested in a specific line, >> we can set the line number to vop

[PATCH 31/31] mm, vmstat: Remove zone and node double accounting by approximating retries

The number of LRU pages, dirty pages and writeback pages must be accounted for on both zones and nodes because of the reclaim retry logic, compaction retry logic and highmem calculations all depending on per-zone stats. The retry logic is only critical for allocations that can use any zones.

[PATCH 31/31] mm, vmstat: Remove zone and node double accounting by approximating retries

The number of LRU pages, dirty pages and writeback pages must be accounted for on both zones and nodes because of the reclaim retry logic, compaction retry logic and highmem calculations all depending on per-zone stats. The retry logic is only critical for allocations that can use any zones.

[PATCH 30/31] mm, vmstat: print node-based stats in zoneinfo file

There are a number of stats that were previously accessible via zoneinfo that are now invisible. While it is possible to create a new file for the node stats, this may be missed by users. Instead this patch prints the stats under the first populated zone in /proc/zoneinfo. Signed-off-by: Mel

[PATCH 30/31] mm, vmstat: print node-based stats in zoneinfo file

There are a number of stats that were previously accessible via zoneinfo that are now invisible. While it is possible to create a new file for the node stats, this may be missed by users. Instead this patch prints the stats under the first populated zone in /proc/zoneinfo. Signed-off-by: Mel

Re: [PATCH 6/7] dt-bindings: net: bgmac: add bindings documentation for bgmac

On Friday, July 1, 2016 11:17:25 AM CEST Jon Mason wrote: > On Fri, Jul 1, 2016 at 5:46 AM, Arnd Bergmann wrote: > > On Thursday, June 30, 2016 6:59:13 PM CEST Jon Mason wrote: > >> + > >> +Required properties: > >> + - compatible: "brcm,bgmac-nsp" > >> + - reg:

Re: [PATCH 6/7] dt-bindings: net: bgmac: add bindings documentation for bgmac

On Friday, July 1, 2016 11:17:25 AM CEST Jon Mason wrote: > On Fri, Jul 1, 2016 at 5:46 AM, Arnd Bergmann wrote: > > On Thursday, June 30, 2016 6:59:13 PM CEST Jon Mason wrote: > >> + > >> +Required properties: > >> + - compatible: "brcm,bgmac-nsp" > >> + - reg:Address and length

[PATCH 15/31] mm, page_alloc: consider dirtyable memory in terms of nodes

Historically dirty pages were spread among zones but now that LRUs are per-node it is more appropriate to consider dirty pages in a node. Link: http://lkml.kernel.org/r/1466518566-30034-16-git-send-email-mgor...@techsingularity.net Signed-off-by: Mel Gorman

[PATCH 15/31] mm, page_alloc: consider dirtyable memory in terms of nodes

Historically dirty pages were spread among zones but now that LRUs are per-node it is more appropriate to consider dirty pages in a node. Link: http://lkml.kernel.org/r/1466518566-30034-16-git-send-email-mgor...@techsingularity.net Signed-off-by: Mel Gorman Signed-off-by: Johannes Weiner

[PATCH 13/31] mm, memcg: move memcg limit enforcement from zones to nodes

Memcg needs adjustment after moving LRUs to the node. Limits are tracked per memcg but the soft-limit excess is tracked per zone. As global page reclaim is based on the node, it is easy to imagine a situation where a zone soft limit is exceeded even though the memcg limit is fine. This patch

[PATCH 24/31] mm, vmscan: Avoid passing in classzone_idx unnecessarily to compaction_ready

The scan_control structure has enough information available for compaction_ready() to make a decision. The classzone_idx manipulations in shrink_zones() are no longer necessary as the highest populated zone is no longer used to determine if shrink_slab should be called or not. Signed-off-by: Mel

[PATCH 23/31] mm, vmscan: Avoid passing in classzone_idx unnecessarily to shrink_node

shrink_node receives all information it needs about classzone_idx from sc->reclaim_idx so remove the aliases. Signed-off-by: Mel Gorman --- mm/vmscan.c | 20 +--- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/mm/vmscan.c

mm: BUG in page_move_anon_rmap

Hello, I am getting the following crashes while running syzkaller fuzzer on 00bf377d19ad3d80cbc7a036521279a86e397bfb (Jun 29). So far I did not manage to reproduce it outside of fuzzer, but fuzzer hits it once per hour or so. flags:

[PATCH 18/31] mm: move most file-based accounting to the node

There are now a number of accounting oddities such as mapped file pages being accounted for on the node while the total number of file pages are accounted on the zone. This can be coped with to some extent but it's confusing so this patch moves the relevant file-based accounted. Due to throttling

[PATCH 22/31] mm: convert zone_reclaim to node_reclaim

As reclaim is now per-node based, convert zone_reclaim to be node_reclaim. It is possible that a node will be reclaimed multiple times if it has multiple zones but this is unavoidable without caching all nodes traversed so far. The documentation and interface to userspace is the same from a

Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible

On Thu, Jun 30, 2016 at 03:53:27PM -0700, Luis R. Rodriguez wrote: > copyleft-next [0] [1] is an openly evolved copyleft license, its an > effort to evolve copyleft without participation of the Church (TM) > or State (R), completley openly to the extend development and > discussion of

[PATCH 21/31] mm, page_alloc: Wake kswapd based on the highest eligible zone

The ac_classzone_idx is used as the basis for waking kswapd and that is based on the preferred zoneref. If the preferred zoneref's highest zone is lower than what is available on other nodes, it's possible that kswapd is woken on a zone with only higher, but still eligible, zones. As classzone_idx

[PATCH 26/31] mm, page_alloc: remove fair zone allocation policy

The fair zone allocation policy interleaves allocation requests between zones to avoid an age inversion problem whereby new pages are reclaimed to balance a zone. Reclaim is now node-based so this should no longer be an issue and the fair zone allocation policy is not free. This patch removes

[PATCH 25/31] mm, vmscan: add classzone information to tracepoints

This is convenient when tracking down why the skip count is high because it'll show what classzone kswapd woke up at and what zones are being isolated. Link: http://lkml.kernel.org/r/1466518566-30034-24-git-send-email-mgor...@techsingularity.net Signed-off-by: Mel Gorman

[PATCH 29/31] mm: vmstat: account per-zone stalls and pages skipped during reclaim

The vmstat allocstall was fairly useful in the general sense but node-based LRUs change that. It's important to know if a stall was for an address-limited allocation request as this will require skipping pages from other zones. This patch adds pgstall_* counters to replace allocstall. The sum

[PATCH 13/31] mm, memcg: move memcg limit enforcement from zones to nodes

Memcg needs adjustment after moving LRUs to the node. Limits are tracked per memcg but the soft-limit excess is tracked per zone. As global page reclaim is based on the node, it is easy to imagine a situation where a zone soft limit is exceeded even though the memcg limit is fine. This patch

[PATCH 24/31] mm, vmscan: Avoid passing in classzone_idx unnecessarily to compaction_ready

The scan_control structure has enough information available for compaction_ready() to make a decision. The classzone_idx manipulations in shrink_zones() are no longer necessary as the highest populated zone is no longer used to determine if shrink_slab should be called or not. Signed-off-by: Mel

[PATCH 23/31] mm, vmscan: Avoid passing in classzone_idx unnecessarily to shrink_node

shrink_node receives all information it needs about classzone_idx from sc->reclaim_idx so remove the aliases. Signed-off-by: Mel Gorman --- mm/vmscan.c | 20 +--- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git a/mm/vmscan.c b/mm/vmscan.c index

mm: BUG in page_move_anon_rmap

Hello, I am getting the following crashes while running syzkaller fuzzer on 00bf377d19ad3d80cbc7a036521279a86e397bfb (Jun 29). So far I did not manage to reproduce it outside of fuzzer, but fuzzer hits it once per hour or so. flags:

[PATCH 18/31] mm: move most file-based accounting to the node

There are now a number of accounting oddities such as mapped file pages being accounted for on the node while the total number of file pages are accounted on the zone. This can be coped with to some extent but it's confusing so this patch moves the relevant file-based accounted. Due to throttling

[PATCH 22/31] mm: convert zone_reclaim to node_reclaim

As reclaim is now per-node based, convert zone_reclaim to be node_reclaim. It is possible that a node will be reclaimed multiple times if it has multiple zones but this is unavoidable without caching all nodes traversed so far. The documentation and interface to userspace is the same from a

Re: [PATCH v2] module.h: add copyleft-next >= 0.3.1 as GPL compatible

On Thu, Jun 30, 2016 at 03:53:27PM -0700, Luis R. Rodriguez wrote: > copyleft-next [0] [1] is an openly evolved copyleft license, its an > effort to evolve copyleft without participation of the Church (TM) > or State (R), completley openly to the extend development and > discussion of

[PATCH 21/31] mm, page_alloc: Wake kswapd based on the highest eligible zone

The ac_classzone_idx is used as the basis for waking kswapd and that is based on the preferred zoneref. If the preferred zoneref's highest zone is lower than what is available on other nodes, it's possible that kswapd is woken on a zone with only higher, but still eligible, zones. As classzone_idx

[PATCH 26/31] mm, page_alloc: remove fair zone allocation policy

The fair zone allocation policy interleaves allocation requests between zones to avoid an age inversion problem whereby new pages are reclaimed to balance a zone. Reclaim is now node-based so this should no longer be an issue and the fair zone allocation policy is not free. This patch removes

[PATCH 25/31] mm, vmscan: add classzone information to tracepoints

This is convenient when tracking down why the skip count is high because it'll show what classzone kswapd woke up at and what zones are being isolated. Link: http://lkml.kernel.org/r/1466518566-30034-24-git-send-email-mgor...@techsingularity.net Signed-off-by: Mel Gorman Acked-by: Vlastimil

[PATCH 29/31] mm: vmstat: account per-zone stalls and pages skipped during reclaim

The vmstat allocstall was fairly useful in the general sense but node-based LRUs change that. It's important to know if a stall was for an address-limited allocation request as this will require skipping pages from other zones. This patch adds pgstall_* counters to replace allocstall. The sum

[PATCH 17/31] mm: rename NR_ANON_PAGES to NR_ANON_MAPPED

NR_FILE_PAGES is the number offile pages. NR_FILE_MAPPED is the number of mapped file pages. NR_ANON_PAGES is the number of mapped anon pages. This is unhelpful naming as it's easy to confuse NR_FILE_MAPPED and NR_ANON_PAGES for mapped pages. This patch renames NR_ANON_PAGES so we have

[PATCH 27/31] mm: page_alloc: cache the last node whose dirty limit is reached

If a page is about to be dirtied then the page allocator attempts to limit the total number of dirty pages that exists in any given zone. The call to node_dirty_ok is expensive so this patch records if the last pgdat examined hit the dirty limits. In some cases, this reduces the number of calls

[PATCH 14/31] mm, workingset: make working set detection node-aware

Working set and refault detection is still zone-based, fix it. Link: http://lkml.kernel.org/r/1466518566-30034-15-git-send-email-mgor...@techsingularity.net Signed-off-by: Mel Gorman Acked-by: Johannes Weiner Acked-by: Vlastimil Babka

[PATCH 17/31] mm: rename NR_ANON_PAGES to NR_ANON_MAPPED

NR_FILE_PAGES is the number offile pages. NR_FILE_MAPPED is the number of mapped file pages. NR_ANON_PAGES is the number of mapped anon pages. This is unhelpful naming as it's easy to confuse NR_FILE_MAPPED and NR_ANON_PAGES for mapped pages. This patch renames NR_ANON_PAGES so we have

[PATCH 27/31] mm: page_alloc: cache the last node whose dirty limit is reached

If a page is about to be dirtied then the page allocator attempts to limit the total number of dirty pages that exists in any given zone. The call to node_dirty_ok is expensive so this patch records if the last pgdat examined hit the dirty limits. In some cases, this reduces the number of calls

[PATCH 14/31] mm, workingset: make working set detection node-aware

Working set and refault detection is still zone-based, fix it. Link: http://lkml.kernel.org/r/1466518566-30034-15-git-send-email-mgor...@techsingularity.net Signed-off-by: Mel Gorman Acked-by: Johannes Weiner Acked-by: Vlastimil Babka Cc: Rik van Riel Signed-off-by: Andrew Morton ---

[PATCH 28/31] mm: vmstat: replace __count_zone_vm_events with a zone id equivalent

This is partially a preparation patch for more vmstat work but it also has the slight advantage that __count_zid_vm_events is cheaper to calculate than __count_zone_vm_events(). Link: http://lkml.kernel.org/r/1466518566-30034-27-git-send-email-mgor...@techsingularity.net Signed-off-by: Mel

[PATCH 19/31] mm: move vmscan writes and file write accounting to the node

As reclaim is now node-based, it follows that page write activity due to page reclaim should also be accounted for on the node. For consistency, also account page writes and page dirtying on a per-node basis. After this patch, there are a few remaining zone counters that may appear strange but

[PATCH 16/31] mm: move page mapped accounting to the node

Reclaim makes decisions based on the number of pages that are mapped but it's mixing node and zone information. Account NR_FILE_MAPPED and NR_ANON_PAGES pages on the node. Link: http://lkml.kernel.org/r/1466518566-30034-17-git-send-email-mgor...@techsingularity.net Signed-off-by: Mel Gorman

[PATCH 20/31] mm, vmscan: only wakeup kswapd once per node for the requested classzone

kswapd is woken when zones are below the low watermark but the wakeup decision is not taking the classzone into account. Now that reclaim is node-based, it is only required to wake kswapd once per node and only if all zones are unbalanced for the requested classzone. Note that one node might be

[PATCH 28/31] mm: vmstat: replace __count_zone_vm_events with a zone id equivalent

This is partially a preparation patch for more vmstat work but it also has the slight advantage that __count_zid_vm_events is cheaper to calculate than __count_zone_vm_events(). Link: http://lkml.kernel.org/r/1466518566-30034-27-git-send-email-mgor...@techsingularity.net Signed-off-by: Mel

[PATCH 19/31] mm: move vmscan writes and file write accounting to the node

As reclaim is now node-based, it follows that page write activity due to page reclaim should also be accounted for on the node. For consistency, also account page writes and page dirtying on a per-node basis. After this patch, there are a few remaining zone counters that may appear strange but

[PATCH 16/31] mm: move page mapped accounting to the node

Reclaim makes decisions based on the number of pages that are mapped but it's mixing node and zone information. Account NR_FILE_MAPPED and NR_ANON_PAGES pages on the node. Link: http://lkml.kernel.org/r/1466518566-30034-17-git-send-email-mgor...@techsingularity.net Signed-off-by: Mel Gorman

[PATCH 20/31] mm, vmscan: only wakeup kswapd once per node for the requested classzone

kswapd is woken when zones are below the low watermark but the wakeup decision is not taking the classzone into account. Now that reclaim is node-based, it is only required to wake kswapd once per node and only if all zones are unbalanced for the requested classzone. Note that one node might be

[PATCH 01/31] mm, vmstat: add infrastructure for per-node vmstats

Series: "Move LRU page reclaim from zones to nodes v7" This is the latest version of a series that moves LRUs from the zones to the node that is based upon 4.6-rc3 plus the page allocator optimisation series. Conceptually, this is simple but there are a lot of details. Some of the broad

[PATCH 04/31] mm, vmscan: begin reclaiming pages on a per-node basis

This patch makes reclaim decisions on a per-node basis. A reclaimer knows what zone is required by the allocation request and skips pages from higher zones. In many cases this will be ok because it's a GFP_HIGHMEM request of some description. On 64-bit, ZONE_DMA32 requests will cause some

<    1   2   3   4   5   6   7   8   9   10   >