From mboxrd@z Thu Jan 1 00:00:00 1970 From: Linus Torvalds Subject: Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR Date: Wed, 11 Jan 2017 11:39:01 -0800 Message-ID: References: <5a3dcc25-b264-37c7-c090-09981b23940d@intel.com> <20170105192910.q26ozg4ci4i3j2ai@black.fi.intel.com> <161ece66-fbf4-cb89-3da6-91b4851af69f@intel.com> <978d5f1a-ec4d-f747-93fd-27ecfe10cb88@intel.com> <20170111142904.GD4895@node.shutemov.name> <20170111183750.GE4895@node.shutemov.name> <0a6f1ee4-e260-ae7b-3d39-c53f6bed8102@intel.com> <20170111193201.GF4895@node.shutemov.name> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <20170111193201.GF4895@node.shutemov.name> Sender: owner-linux-mm@kvack.org To: "Kirill A. Shutemov" Cc: Andy Lutomirski , Dave Hansen , "Kirill A. Shutemov" , Andrew Morton , X86 ML , Thomas Gleixner , Ingo Molnar , Arnd Bergmann , "H. Peter Anvin" , Andi Kleen , linux-arch , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , Linux API List-Id: linux-arch.vger.kernel.org On Wed, Jan 11, 2017 at 11:32 AM, Kirill A. Shutemov wrote: > > Running legacy binary with full address space is valuable option. I disagree. It's simply not valuable enough to worry about. Especially when there is a fairly trivial wrapper approach: just make a full-address-space wrapper than acts as a binary loader (think "specialized ld.so"). Sure, the wrapper may be "fairly trivial" but not necessarily pleasant: you have to parse ELF sections etc and basically load the binary by hand. But there are libraries for that, and loading an ELF executable isn't rocket surgery, it's just possibly tedious. Linus -- 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: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-io0-f195.google.com ([209.85.223.195]:35596 "EHLO mail-io0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932560AbdAKTjD (ORCPT ); Wed, 11 Jan 2017 14:39:03 -0500 MIME-Version: 1.0 In-Reply-To: <20170111193201.GF4895@node.shutemov.name> References: <5a3dcc25-b264-37c7-c090-09981b23940d@intel.com> <20170105192910.q26ozg4ci4i3j2ai@black.fi.intel.com> <161ece66-fbf4-cb89-3da6-91b4851af69f@intel.com> <978d5f1a-ec4d-f747-93fd-27ecfe10cb88@intel.com> <20170111142904.GD4895@node.shutemov.name> <20170111183750.GE4895@node.shutemov.name> <0a6f1ee4-e260-ae7b-3d39-c53f6bed8102@intel.com> <20170111193201.GF4895@node.shutemov.name> From: Linus Torvalds Date: Wed, 11 Jan 2017 11:39:01 -0800 Message-ID: Subject: Re: [RFC, PATCHv2 29/29] mm, x86: introduce RLIMIT_VADDR Content-Type: text/plain; charset=UTF-8 Sender: linux-arch-owner@vger.kernel.org List-ID: To: "Kirill A. Shutemov" Cc: Andy Lutomirski , Dave Hansen , "Kirill A. Shutemov" , Andrew Morton , X86 ML , Thomas Gleixner , Ingo Molnar , Arnd Bergmann , "H. Peter Anvin" , Andi Kleen , linux-arch , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , Linux API Message-ID: <20170111193901.4QDtJ9gjZs6N_ByKzPjN5Ogi1nujKx5ae5piaIe7Mqo@z> On Wed, Jan 11, 2017 at 11:32 AM, Kirill A. Shutemov wrote: > > Running legacy binary with full address space is valuable option. I disagree. It's simply not valuable enough to worry about. Especially when there is a fairly trivial wrapper approach: just make a full-address-space wrapper than acts as a binary loader (think "specialized ld.so"). Sure, the wrapper may be "fairly trivial" but not necessarily pleasant: you have to parse ELF sections etc and basically load the binary by hand. But there are libraries for that, and loading an ELF executable isn't rocket surgery, it's just possibly tedious. Linus