From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752338AbbF3V3R (ORCPT ); Tue, 30 Jun 2015 17:29:17 -0400 Received: from mail-out.m-online.net ([212.18.0.9]:36616 "EHLO mail-out.m-online.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751459AbbF3V3I (ORCPT ); Tue, 30 Jun 2015 17:29:08 -0400 X-Auth-Info: V2sysJpjN8Kdu8WxdiJnQyJXrxKtXsMf2LQQxmKAY00JAtPKEwYTpkGw4/qA17zH From: Andreas Schwab To: Andy Lutomirski Cc: X86 ML , "linux-kernel\@vger.kernel.org" , Alexander Larsson , Cosimo Cecchi , Dan Nicholson , Network Development , libc-alpha Subject: Re: Wiring up direct socket calls on x86_32 Linux? References: X-Yow: I'm protected by a ROLL-ON I rented from AVIS.. Date: Tue, 30 Jun 2015 23:29:04 +0200 In-Reply-To: (Andy Lutomirski's message of "Tue, 30 Jun 2015 14:14:38 -0700") Message-ID: <87oajwrilb.fsf@igel.home> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andy Lutomirski writes: > Glibc people: If Linux wired up the syscalls, would glibc use them? Not automatically. It needs to be compatible with the configured minimum kernel version, so runtime probing would needed to be implemented. Andreas. -- Andreas Schwab, schwab@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."