Date: Sun, 21 Feb 2010 22:21:22 -0800 (PST)
Message-Id: <20100221.222122.193722153.davem@davemloft.net>
To: weigelt@metux.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dynamic linking in the kernel
From: David Miller <davem@davemloft.net>
In-Reply-To: <4B82197F.4050902@metux.de>
References: <4B802870.5030201@metux.de>
	<20100220.125758.174837163.davem@davemloft.net>
	<4B82197F.4050902@metux.de>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1018
Lines: 26

From: Enrico Weigelt <weigelt@metux.de>
Date: Mon, 22 Feb 2010 06:43:27 +0100

> David Miller wrote:
> 
>> In order to implement this the kernel would have to also save a copy
>> of all pieces of the processes's environment and compare all of the
>> environment variable settings on every execution.  This would be
>> needed to handle things like LD_PRELOAD, LD_LIBRARY_PATH, and LD_DEBUG
>> as just three examples.
> 
> Fairly simple:
> 
> * parsed per-module data is cached by its inode id
> * cached data that can be influenced by LD_PRELOAD/LD_LIBRARY_PATH
>   (eg. mapping of library names to actual filenames or inode-id's)
>   is cached on hash of these variables plus inode-id

Feel free to implement this and show us the numbers.

I am not as confident as you :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/