From: Michal Hocko <mhocko@kernel.org> To: Andrew Morton <akpm@linux-foundation.org> Cc: Vlastimil Babka <vbabka@suse.cz>, David Rientjes <rientjes@google.com>, Mel Gorman <mgorman@suse.de>, Johannes Weiner <hannes@cmpxchg.org>, Al Viro <viro@zeniv.linux.org.uk>, <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>, Andreas Dilger <adilger@dilger.ca>, Andreas Dilger <andreas.dilger@intel.com>, Andrey Konovalov <andreyknvl@google.com>, Anton Vorontsov <anton@enomsg.org>, Ben Skeggs <bskeggs@redhat.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>, Christian Borntraeger <borntraeger@de.ibm.com>, Colin Cross <ccross@android.com>, Daniel Borkmann <daniel@iogearbox.net>, Dan Williams <dan.j.williams@intel.com>, David Sterba <dsterba@suse.com>, Eric Dumazet <edumazet@google.com>, Eric Dumazet <eric.dumazet@gmail.com>, Hariprasad S <hariprasad@chelsio.com>, Heiko Carstens <heiko.carstens@de.ibm.com>, Herbert Xu <herbert@gondor.apana.org.au>, Ilya Dryomov <idryomov@gmail.com>, John Hubbard <jhubbard@nvidia.com>, Kees Cook <keescook@chromium.org>, Kent Overstreet <kent.overstreet@gmail.com>, Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>, Martin Schwidefsky <schwidefsky@de.ibm.com>, "Michael S. Tsirkin" <mst@redhat.com>, Michal Hocko <mhocko@suse.com>, Mike Snitzer <snitzer@redhat.com>, Mikulas Patocka <mpatocka@redhat.com>, Oleg Drokin <oleg.drokin@intel.com>, Pablo Neira Ayuso <pablo@netfilter.org>, "Rafael J. Wysocki" <rjw@rjwysocki.net>, Santosh Raspatur <santosh@chelsio.com>, Tariq Toukan <tariqt@mellanox.com>, Tom Herbert <tom@herbertland.com>, Tony Luck <tony.luck@intel.com>, "Yan, Zheng" <zyan@redhat.com>, Yishai Hadas <yishaih@mellanox.com> Subject: [PATCH 0/6 v3] kvmalloc Date: Mon, 30 Jan 2017 10:49:31 +0100 [thread overview] Message-ID: <20170130094940.13546-1-mhocko@kernel.org> (raw) Hi, this has been previously posted here [1] and it received quite some feedback. As a result the number of patches has grown again. We are at 9 patches right now. I have rebased the series on top of the current next-20170130. There were some changes since the last posting, namely a7f6c1b63b86 ("AppArmor: Use GFP_KERNEL for __aa_kvmalloc().") which dropped GFP_NOIO from __aa_kvmalloc and d407bd25a204 ("bpf: don't trigger OOM killer under pressure with map alloc") which has created a kvmalloc alternative for bpf code. Both have been changed to use the mm kvmalloc but it is worth noting this dependency during the merge window. I hope there are no further obstacles to have this merged into the mmotm tree and go in in the next merge window. Original cover: There are many open coded kmalloc with vmalloc fallback instances in the tree. Most of them are not careful enough or simply do not care about the underlying semantic of the kmalloc/page allocator which means that a) some vmalloc fallbacks are basically unreachable because the kmalloc part will keep retrying until it succeeds b) the page allocator can invoke a really disruptive steps like the OOM killer to move forward which doesn't sound appropriate when we consider that the vmalloc fallback is available. As it can be seen implementing kvmalloc requires quite an intimate knowledge if the page allocator and the memory reclaim internals which strongly suggests that a helper should be implemented in the memory subsystem proper. Most callers, I could find, have been converted to use the helper instead. This is patch 5. There are some more relying on __GFP_REPEAT in the networking stack which I have converted as well and Eric Dumazet was not opposed [2] to convert them as well. [1] http://lkml.kernel.org/r/20170112153717.28943-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/1485273626.16328.301.camel@edumazet-glaptop3.roam.corp.google.com Michal Hocko (9): mm: introduce kv[mz]alloc helpers mm: support __GFP_REPEAT in kvmalloc_node for >32kB rhashtable: simplify a strange allocation pattern ila: simplify a strange allocation pattern treewide: use kv[mz]alloc* rather than opencoded variants net: use kvmalloc with __GFP_REPEAT rather than open coded variant md: use kvmalloc rather than opencoded variant bcache: use kvmalloc net, bpf: use kvzalloc helper arch/s390/kvm/kvm-s390.c | 10 +--- arch/x86/kvm/lapic.c | 4 +- arch/x86/kvm/page_track.c | 4 +- arch/x86/kvm/x86.c | 4 +- crypto/lzo.c | 4 +- drivers/acpi/apei/erst.c | 8 +-- drivers/char/agp/generic.c | 8 +-- drivers/gpu/drm/nouveau/nouveau_gem.c | 4 +- drivers/md/bcache/super.c | 8 +-- drivers/md/bcache/util.h | 12 +---- drivers/md/dm-ioctl.c | 13 ++--- drivers/md/dm-stats.c | 7 +-- drivers/net/ethernet/chelsio/cxgb3/cxgb3_defs.h | 3 -- drivers/net/ethernet/chelsio/cxgb3/cxgb3_offload.c | 29 ++--------- drivers/net/ethernet/chelsio/cxgb3/l2t.c | 8 +-- drivers/net/ethernet/chelsio/cxgb3/l2t.h | 1 - drivers/net/ethernet/chelsio/cxgb4/clip_tbl.c | 12 ++--- drivers/net/ethernet/chelsio/cxgb4/cxgb4.h | 3 -- drivers/net/ethernet/chelsio/cxgb4/cxgb4_debugfs.c | 10 ++-- drivers/net/ethernet/chelsio/cxgb4/cxgb4_ethtool.c | 8 +-- drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c | 31 ++---------- drivers/net/ethernet/chelsio/cxgb4/cxgb4_tc_u32.c | 13 +++-- drivers/net/ethernet/chelsio/cxgb4/l2t.c | 2 +- drivers/net/ethernet/chelsio/cxgb4/sched.c | 12 ++--- drivers/net/ethernet/mellanox/mlx4/en_tx.c | 9 ++-- drivers/net/ethernet/mellanox/mlx4/mr.c | 9 ++-- drivers/nvdimm/dimm_devs.c | 5 +- .../staging/lustre/lnet/libcfs/linux/linux-mem.c | 11 +---- drivers/vhost/net.c | 9 ++-- drivers/vhost/vhost.c | 15 ++---- drivers/vhost/vsock.c | 9 ++-- drivers/xen/evtchn.c | 14 +----- fs/btrfs/ctree.c | 9 ++-- fs/btrfs/ioctl.c | 9 ++-- fs/btrfs/send.c | 27 ++++------ fs/ceph/file.c | 9 ++-- fs/ext4/mballoc.c | 2 +- fs/ext4/super.c | 4 +- fs/f2fs/f2fs.h | 20 -------- fs/f2fs/file.c | 4 +- fs/f2fs/segment.c | 14 +++--- fs/select.c | 5 +- fs/seq_file.c | 16 +----- fs/xattr.c | 27 ++++------ include/linux/kvm_host.h | 2 - include/linux/mlx5/driver.h | 7 +-- include/linux/mm.h | 22 +++++++++ include/linux/vmalloc.h | 1 + ipc/util.c | 7 +-- kernel/bpf/syscall.c | 19 ++------ lib/iov_iter.c | 5 +- lib/rhashtable.c | 13 ++--- mm/frame_vector.c | 5 +- mm/nommu.c | 5 ++ mm/util.c | 57 ++++++++++++++++++++++ mm/vmalloc.c | 9 +++- net/core/dev.c | 24 ++++----- net/ipv4/inet_hashtables.c | 6 +-- net/ipv4/tcp_metrics.c | 5 +- net/ipv6/ila/ila_xlat.c | 8 +-- net/mpls/af_mpls.c | 5 +- net/netfilter/x_tables.c | 37 ++++---------- net/netfilter/xt_recent.c | 5 +- net/sched/sch_choke.c | 5 +- net/sched/sch_fq.c | 12 +---- net/sched/sch_fq_codel.c | 26 +++------- net/sched/sch_hhf.c | 33 ++++--------- net/sched/sch_netem.c | 6 +-- net/sched/sch_sfq.c | 6 +-- security/apparmor/apparmorfs.c | 2 +- security/apparmor/include/lib.h | 11 ----- security/apparmor/lib.c | 30 ------------ security/apparmor/match.c | 2 +- security/apparmor/policy_unpack.c | 2 +- security/keys/keyctl.c | 22 +++------ virt/kvm/kvm_main.c | 18 ++----- 76 files changed, 279 insertions(+), 583 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org> To: Andrew Morton <akpm@linux-foundation.org> Cc: Vlastimil Babka <vbabka@suse.cz>, David Rientjes <rientjes@google.com>, Mel Gorman <mgorman@suse.de>, Johannes Weiner <hannes@cmpxchg.org>, Al Viro <viro@zeniv.linux.org.uk>, linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>, Andreas Dilger <adilger@dilger.ca>, Andreas Dilger <andreas.dilger@intel.com>, Andrey Konovalov <andreyknvl@google.com>, Anton Vorontsov <anton@enomsg.org>, Ben Skeggs <bskeggs@redhat.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>, Christian Borntraeger <borntraeger@de.ibm.com>, Colin Cross <ccross@android.com>, Daniel Borkmann <daniel@iogearbox.net>, Dan Williams <dan.j.williams@intel.com>, David Sterba <dsterba@suse.com>, Eric Dumazet <edumazet@google.com>, Eric Dumazet <eric.dumazet@gmail.com>, Hariprasad S <hariprasad@chelsio.com>, Heiko Carstens <heiko.carstens@de.ibm.com>, Herbert Xu <herbert@gondor.apana.org.au>, Ilya Dryomov <idryomov@gmail.com>, John Hubbard <jhubbard@nvidia.com>, Kees Cook <keescook@chromium.org>, Kent Overstreet <kent.overstreet@gmail.com>, Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>, Martin Schwidefsky <schwidefsky@de.ibm.com>, "Michael S. Tsirkin" <mst@redhat.com>, Michal Hocko <mhocko@suse.com>, Mike Snitzer <snitzer@redhat.com>, Mikulas Patocka <mpatocka@redhat.com>, Oleg Drokin <oleg.drokin@intel.com>, Pablo Neira Ayuso <pablo@netfilter.org>, "Rafael J. Wysocki" <rjw@rjwysocki.net>, Santosh Raspatur <santosh@chelsio.com>, Tariq Toukan <tariqt@mellanox.com>, Tom Herbert <tom@herbertland.com>, Tony Luck <tony.luck@intel.com>, "Yan, Zheng" <zyan@redhat.com>, Yishai Hadas <yishaih@mellanox.com> Subject: [PATCH 0/6 v3] kvmalloc Date: Mon, 30 Jan 2017 10:49:31 +0100 [thread overview] Message-ID: <20170130094940.13546-1-mhocko@kernel.org> (raw) Hi, this has been previously posted here [1] and it received quite some feedback. As a result the number of patches has grown again. We are at 9 patches right now. I have rebased the series on top of the current next-20170130. There were some changes since the last posting, namely a7f6c1b63b86 ("AppArmor: Use GFP_KERNEL for __aa_kvmalloc().") which dropped GFP_NOIO from __aa_kvmalloc and d407bd25a204 ("bpf: don't trigger OOM killer under pressure with map alloc") which has created a kvmalloc alternative for bpf code. Both have been changed to use the mm kvmalloc but it is worth noting this dependency during the merge window. I hope there are no further obstacles to have this merged into the mmotm tree and go in in the next merge window. Original cover: There are many open coded kmalloc with vmalloc fallback instances in the tree. Most of them are not careful enough or simply do not care about the underlying semantic of the kmalloc/page allocator which means that a) some vmalloc fallbacks are basically unreachable because the kmalloc part will keep retrying until it succeeds b) the page allocator can invoke a really disruptive steps like the OOM killer to move forward which doesn't sound appropriate when we consider that the vmalloc fallback is available. As it can be seen implementing kvmalloc requires quite an intimate knowledge if the page allocator and the memory reclaim internals which strongly suggests that a helper should be implemented in the memory subsystem proper. Most callers, I could find, have been converted to use the helper instead. This is patch 5. There are some more relying on __GFP_REPEAT in the networking stack which I have converted as well and Eric Dumazet was not opposed [2] to convert them as well. [1] http://lkml.kernel.org/r/20170112153717.28943-1-mhocko@kernel.org [2] http://lkml.kernel.org/r/1485273626.16328.301.camel@edumazet-glaptop3.roam.corp.google.com Michal Hocko (9): mm: introduce kv[mz]alloc helpers mm: support __GFP_REPEAT in kvmalloc_node for >32kB rhashtable: simplify a strange allocation pattern ila: simplify a strange allocation pattern treewide: use kv[mz]alloc* rather than opencoded variants net: use kvmalloc with __GFP_REPEAT rather than open coded variant md: use kvmalloc rather than opencoded variant bcache: use kvmalloc net, bpf: use kvzalloc helper arch/s390/kvm/kvm-s390.c | 10 +--- arch/x86/kvm/lapic.c | 4 +- arch/x86/kvm/page_track.c | 4 +- arch/x86/kvm/x86.c | 4 +- crypto/lzo.c | 4 +- drivers/acpi/apei/erst.c | 8 +-- drivers/char/agp/generic.c | 8 +-- drivers/gpu/drm/nouveau/nouveau_gem.c | 4 +- drivers/md/bcache/super.c | 8 +-- drivers/md/bcache/util.h | 12 +---- drivers/md/dm-ioctl.c | 13 ++--- drivers/md/dm-stats.c | 7 +-- drivers/net/ethernet/chelsio/cxgb3/cxgb3_defs.h | 3 -- drivers/net/ethernet/chelsio/cxgb3/cxgb3_offload.c | 29 ++--------- drivers/net/ethernet/chelsio/cxgb3/l2t.c | 8 +-- drivers/net/ethernet/chelsio/cxgb3/l2t.h | 1 - drivers/net/ethernet/chelsio/cxgb4/clip_tbl.c | 12 ++--- drivers/net/ethernet/chelsio/cxgb4/cxgb4.h | 3 -- drivers/net/ethernet/chelsio/cxgb4/cxgb4_debugfs.c | 10 ++-- drivers/net/ethernet/chelsio/cxgb4/cxgb4_ethtool.c | 8 +-- drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c | 31 ++---------- drivers/net/ethernet/chelsio/cxgb4/cxgb4_tc_u32.c | 13 +++-- drivers/net/ethernet/chelsio/cxgb4/l2t.c | 2 +- drivers/net/ethernet/chelsio/cxgb4/sched.c | 12 ++--- drivers/net/ethernet/mellanox/mlx4/en_tx.c | 9 ++-- drivers/net/ethernet/mellanox/mlx4/mr.c | 9 ++-- drivers/nvdimm/dimm_devs.c | 5 +- .../staging/lustre/lnet/libcfs/linux/linux-mem.c | 11 +---- drivers/vhost/net.c | 9 ++-- drivers/vhost/vhost.c | 15 ++---- drivers/vhost/vsock.c | 9 ++-- drivers/xen/evtchn.c | 14 +----- fs/btrfs/ctree.c | 9 ++-- fs/btrfs/ioctl.c | 9 ++-- fs/btrfs/send.c | 27 ++++------ fs/ceph/file.c | 9 ++-- fs/ext4/mballoc.c | 2 +- fs/ext4/super.c | 4 +- fs/f2fs/f2fs.h | 20 -------- fs/f2fs/file.c | 4 +- fs/f2fs/segment.c | 14 +++--- fs/select.c | 5 +- fs/seq_file.c | 16 +----- fs/xattr.c | 27 ++++------ include/linux/kvm_host.h | 2 - include/linux/mlx5/driver.h | 7 +-- include/linux/mm.h | 22 +++++++++ include/linux/vmalloc.h | 1 + ipc/util.c | 7 +-- kernel/bpf/syscall.c | 19 ++------ lib/iov_iter.c | 5 +- lib/rhashtable.c | 13 ++--- mm/frame_vector.c | 5 +- mm/nommu.c | 5 ++ mm/util.c | 57 ++++++++++++++++++++++ mm/vmalloc.c | 9 +++- net/core/dev.c | 24 ++++----- net/ipv4/inet_hashtables.c | 6 +-- net/ipv4/tcp_metrics.c | 5 +- net/ipv6/ila/ila_xlat.c | 8 +-- net/mpls/af_mpls.c | 5 +- net/netfilter/x_tables.c | 37 ++++---------- net/netfilter/xt_recent.c | 5 +- net/sched/sch_choke.c | 5 +- net/sched/sch_fq.c | 12 +---- net/sched/sch_fq_codel.c | 26 +++------- net/sched/sch_hhf.c | 33 ++++--------- net/sched/sch_netem.c | 6 +-- net/sched/sch_sfq.c | 6 +-- security/apparmor/apparmorfs.c | 2 +- security/apparmor/include/lib.h | 11 ----- security/apparmor/lib.c | 30 ------------ security/apparmor/match.c | 2 +- security/apparmor/policy_unpack.c | 2 +- security/keys/keyctl.c | 22 +++------ virt/kvm/kvm_main.c | 18 ++----- 76 files changed, 279 insertions(+), 583 deletions(-) -- 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>
next reply other threads:[~2017-01-30 9:50 UTC|newest] Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-01-30 9:49 Michal Hocko [this message] 2017-01-30 9:49 ` [PATCH 0/6 v3] kvmalloc Michal Hocko 2017-01-30 9:49 ` [PATCH 1/9] mm: introduce kv[mz]alloc helpers Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 9:49 ` [PATCH 2/9] mm: support __GFP_REPEAT in kvmalloc_node for >32kB Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 9:49 ` [PATCH 3/9] rhashtable: simplify a strange allocation pattern Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 14:04 ` Vlastimil Babka 2017-01-30 14:04 ` Vlastimil Babka 2017-01-30 9:49 ` [PATCH 4/9] ila: " Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 15:21 ` Vlastimil Babka 2017-01-30 15:21 ` Vlastimil Babka 2017-01-30 9:49 ` [PATCH 5/9] treewide: use kv[mz]alloc* rather than opencoded variants Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 10:21 ` Leon Romanovsky 2017-01-30 10:21 ` Leon Romanovsky 2017-01-30 16:14 ` Vlastimil Babka 2017-01-30 16:14 ` Vlastimil Babka 2017-01-30 16:14 ` Vlastimil Babka 2017-01-30 19:24 ` Kees Cook 2017-01-30 19:24 ` Kees Cook 2017-01-30 19:24 ` Kees Cook 2017-01-30 9:49 ` [PATCH 6/9] net: use kvmalloc with __GFP_REPEAT rather than open coded variant Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 16:36 ` Vlastimil Babka 2017-01-30 16:36 ` Vlastimil Babka 2017-01-30 9:49 ` [PATCH 7/9] md: use kvmalloc rather than opencoded variant Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 16:42 ` Vlastimil Babka 2017-01-30 16:42 ` Vlastimil Babka 2017-02-01 17:29 ` Mikulas Patocka 2017-02-01 17:29 ` Mikulas Patocka 2017-02-01 17:58 ` Michal Hocko 2017-02-01 17:58 ` Michal Hocko 2017-01-30 9:49 ` [PATCH 8/9] bcache: use kvmalloc Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 16:47 ` Vlastimil Babka 2017-01-30 16:47 ` Vlastimil Babka 2017-01-30 17:25 ` Michal Hocko 2017-01-30 17:25 ` Michal Hocko 2017-01-30 9:49 ` [PATCH 9/9] net, bpf: use kvzalloc helper Michal Hocko 2017-01-30 9:49 ` Michal Hocko 2017-01-30 17:20 ` Michal Hocko 2017-01-30 17:20 ` Michal Hocko 2017-02-05 10:23 ` [PATCH 0/6 v3] kvmalloc Michal Hocko 2017-02-05 10:23 ` Michal Hocko -- strict thread matches above, loose matches on Subject: below -- 2017-01-25 18:14 Alexei Starovoitov 2017-01-25 18:14 ` Alexei Starovoitov 2017-01-25 20:16 ` Daniel Borkmann 2017-01-25 20:16 ` Daniel Borkmann 2017-01-26 7:43 ` Michal Hocko 2017-01-26 7:43 ` Michal Hocko 2017-01-26 9:36 ` Daniel Borkmann 2017-01-26 9:36 ` Daniel Borkmann 2017-01-26 9:48 ` David Laight 2017-01-26 9:48 ` David Laight 2017-01-26 10:08 ` Michal Hocko 2017-01-26 10:08 ` Michal Hocko 2017-01-26 10:32 ` Michal Hocko 2017-01-26 10:32 ` Michal Hocko 2017-01-26 11:04 ` Daniel Borkmann 2017-01-26 11:04 ` Daniel Borkmann 2017-01-26 11:49 ` Michal Hocko 2017-01-26 11:49 ` Michal Hocko 2017-01-26 12:14 ` Joe Perches 2017-01-26 12:14 ` Joe Perches 2017-01-26 12:27 ` Michal Hocko 2017-01-26 12:27 ` Michal Hocko 2017-01-26 11:33 ` Daniel Borkmann 2017-01-26 11:33 ` Daniel Borkmann 2017-01-26 11:58 ` Michal Hocko 2017-01-26 11:58 ` Michal Hocko 2017-01-26 13:10 ` Daniel Borkmann 2017-01-26 13:10 ` Daniel Borkmann 2017-01-26 13:40 ` Michal Hocko 2017-01-26 13:40 ` Michal Hocko 2017-01-26 14:13 ` Michal Hocko 2017-01-26 14:13 ` Michal Hocko 2017-01-26 14:13 ` Michal Hocko 2017-01-26 20:34 ` Daniel Borkmann 2017-01-26 20:34 ` Daniel Borkmann 2017-01-27 10:05 ` Michal Hocko 2017-01-27 10:05 ` Michal Hocko 2017-01-27 20:12 ` Daniel Borkmann 2017-01-27 20:12 ` Daniel Borkmann 2017-01-30 7:56 ` Michal Hocko 2017-01-30 7:56 ` Michal Hocko 2017-01-30 16:15 ` Daniel Borkmann 2017-01-30 16:15 ` Daniel Borkmann 2017-01-30 16:28 ` Michal Hocko 2017-01-30 16:28 ` Michal Hocko 2017-01-30 16:45 ` Daniel Borkmann 2017-01-30 16:45 ` Daniel Borkmann 2017-01-12 15:37 Michal Hocko 2017-01-12 15:37 ` Michal Hocko 2017-01-24 15:17 ` Michal Hocko 2017-01-24 15:17 ` Michal Hocko 2017-01-24 16:00 ` Eric Dumazet 2017-01-24 16:00 ` Eric Dumazet 2017-01-25 13:10 ` Michal Hocko 2017-01-25 13:10 ` Michal Hocko 2017-01-24 19:17 ` Alexei Starovoitov 2017-01-24 19:17 ` Alexei Starovoitov 2017-01-25 13:10 ` Michal Hocko 2017-01-25 13:10 ` Michal Hocko 2017-01-25 13:21 ` Michal Hocko 2017-01-25 13:21 ` Michal Hocko
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=20170130094940.13546-1-mhocko@kernel.org \ --to=mhocko@kernel.org \ --cc=adilger@dilger.ca \ --cc=akpm@linux-foundation.org \ --cc=andreas.dilger@intel.com \ --cc=andreyknvl@google.com \ --cc=anton@enomsg.org \ --cc=ast@kernel.org \ --cc=boris.ostrovsky@oracle.com \ --cc=borntraeger@de.ibm.com \ --cc=bskeggs@redhat.com \ --cc=ccross@android.com \ --cc=dan.j.williams@intel.com \ --cc=daniel@iogearbox.net \ --cc=dsterba@suse.com \ --cc=edumazet@google.com \ --cc=eric.dumazet@gmail.com \ --cc=hannes@cmpxchg.org \ --cc=hariprasad@chelsio.com \ --cc=heiko.carstens@de.ibm.com \ --cc=herbert@gondor.apana.org.au \ --cc=idryomov@gmail.com \ --cc=jhubbard@nvidia.com \ --cc=keescook@chromium.org \ --cc=kent.overstreet@gmail.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=marcelo.leitner@gmail.com \ --cc=mgorman@suse.de \ --cc=mhocko@suse.com \ --cc=mpatocka@redhat.com \ --cc=mst@redhat.com \ --cc=oleg.drokin@intel.com \ --cc=pablo@netfilter.org \ --cc=rientjes@google.com \ --cc=rjw@rjwysocki.net \ --cc=santosh@chelsio.com \ --cc=schwidefsky@de.ibm.com \ --cc=snitzer@redhat.com \ --cc=tariqt@mellanox.com \ --cc=tom@herbertland.com \ --cc=tony.luck@intel.com \ --cc=vbabka@suse.cz \ --cc=viro@zeniv.linux.org.uk \ --cc=yishaih@mellanox.com \ --cc=zyan@redhat.com \ /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: linkBe 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.