Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263630AbTEOBt6 (ORCPT ); Wed, 14 May 2003 21:49:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263639AbTEOBt5 (ORCPT ); Wed, 14 May 2003 21:49:57 -0400 Received: from 12-234-34-139.client.attbi.com ([12.234.34.139]:2806 "EHLO heavens.murgatroid.com") by vger.kernel.org with ESMTP id S263630AbTEOBt5 (ORCPT ); Wed, 14 May 2003 21:49:57 -0400 From: "Christopher Hoover" To: "'Davide Libenzi'" , "'Andrew Morton'" Cc: "'Linus Torvalds'" , , , "'Linux Kernel Mailing List'" Subject: RE: [PATCH] 2.5.68 FUTEX support should be optional Date: Wed, 14 May 2003 19:02:37 -0700 Organization: Murgatroid.Com Message-ID: <002901c31a86$0f606020$175e040f@bergamot> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Importance: Normal Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 603 Lines: 18 > This should also break kernels with MMUs ( see mm_release ). I don't believe it does as there's a cond_syscall entry for sys_futex. More to the point, I'm running with CONFIG_FUTEX=n and it works fine. I'm up to a whopping 304KiB MemFree with busybox and bluetooth (hcid/sdpd/hciattach) running. -ch mailto:ch(at)hpl.hp.com mailto:ch(at)murgatroid.com - 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/