X-Original-To: alpine-devel@lists.alpinelinux.org Delivered-To: alpine-devel@lists.alpinelinux.org Received: from mail.wtbts.no (mail.wtbts.no [213.234.126.131]) by lists.alpinelinux.org (Postfix) with ESMTP id A9A2B360F674 for ; Mon, 2 May 2011 13:53:30 +0000 (UTC) Received: from localhost (bsna.nor.wtbts.net [127.0.0.1]) by mail.wtbts.no (Postfix) with ESMTP id 274A1AE4002 for ; Mon, 2 May 2011 13:53:30 +0000 (UTC) X-Virus-Scanned: Yes Received: from mail.wtbts.no ([127.0.0.1]) by localhost (bsna.nor.wtbts.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5xDFKs+B7ZUP for ; Mon, 2 May 2011 13:53:29 +0000 (UTC) Received: from mail.ytre.org (extmail.nor.wtbts.net [10.65.72.14]) by mail.wtbts.no (Postfix) with ESMTP id 98DAEAE4001 for ; Mon, 2 May 2011 13:53:29 +0000 (UTC) Received: from mail.ytre.org (localhost [127.0.0.1]) by mail.ytre.org (Postfix) with ESMTP id 6B572621BD354 for ; Mon, 2 May 2011 13:53:29 +0000 (UTC) Received: from ncopa-desktop.nor.wtbts.net (unknown [10.65.65.1]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: ncopa@ytre.org) by mail.ytre.org (Postfix) with ESMTPSA id 51CC6621BD353 for ; Mon, 2 May 2011 13:53:28 +0000 (UTC) Date: Mon, 2 May 2011 15:50:16 +0200 From: Natanael Copa To: alpine-devel@lists.alpinelinux.org Subject: [alpine-devel] switch to segmexec or stay on 2.6.38.2 Message-ID: <20110502155016.201e8577@ncopa-desktop.nor.wtbts.net> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.0; x86_64-unknown-linux-gnu) X-Mailinglist: alpine-devel Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Hi, So, there is a regression in the pageexec feaure we are using in our kernel config so kernels after 2.6.38.2 does not work (at least not on the VIA cpu's I have tested) So, as I understand, we have the following options: * switch to SEGMEXEC * stay on 2.6.38.2 (til pageexec is fixed) I talked with PAX developer on IRC and it will not be fixed anytime soon, atleast not til the 2.2.0 release tomorrow. The drawback with SEGMEXEC are: * not tested in alpine linux and we release tomorrow. * applications are limited to 1.5GB address space instead of the normal 3GB. The benefit with SEGMEXEC is that there are a theoretical performance increase (i doubt people will notice) So, with SEGMEXEC people who have an application that uses more than 1.5G will break, even if it used to work. Those should probably switch to x86_64 anyways. So what do you guys think: we switch to segmexec now in last minute or we stay on 2.6.38.2? -nc --- Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org Help: alpine-devel+help@lists.alpinelinux.org ---