From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29350 invoked by alias); 10 Jun 2010 15:23:16 -0000 Received: (qmail 28952 invoked by uid 48); 10 Jun 2010 15:22:57 -0000 Date: Thu, 10 Jun 2010 15:23:00 -0000 Message-ID: <20100610152257.28950.qmail@sourceware.org> From: "pasky at suse dot cz" To: glibc-bugs@sources.redhat.com In-Reply-To: <20100610101530.11687.christoph@familiekling.de> References: <20100610101530.11687.christoph@familiekling.de> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug libc/11687] Allow customizing of __FD_SETSIZE X-Bugzilla-Reason: CC Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2010-06/txt/msg00089.txt.bz2 ------- Additional Comments From pasky at suse dot cz 2010-06-10 15:22 ------- You cannot simply change FD_SETSIZE like this and expect anything to work. The FD_SETSIZE value is part of the ABI and depends mainly on the kernel - if you use larger fdset size, the syscall will not work anyway. You would have to hack your kernel too, and then you are completely on your own anyway; other strange problems can also pop up due to different structure sizes in already compiled programs. In short, FD_SETSIZE is not remotely a variable that would be runtime-adjustable, and it's not defined as a fixed value just for the sake of it. If you need to handle more fds, you will need different methods like poll() or epoll(). -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID http://sourceware.org/bugzilla/show_bug.cgi?id=11687 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.