From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/3738 Path: news.gmane.org!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: Proposed roadmap to 1.0 Date: Thu, 25 Jul 2013 03:40:41 -0400 Message-ID: <20130725074040.GE4284@brightrain.aerifal.cx> References: <20130717160204.GF12469@brightrain.aerifal.cx> <1374691013.3031.6@driftwood> <20130724194719.GY3249@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1374738053 2148 80.91.229.3 (25 Jul 2013 07:40:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 25 Jul 2013 07:40:53 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-3742-gllmg-musl=m.gmane.org@lists.openwall.com Thu Jul 25 09:40:54 2013 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1V2GAQ-0000Fv-9F for gllmg-musl@plane.gmane.org; Thu, 25 Jul 2013 09:40:54 +0200 Original-Received: (qmail 24219 invoked by uid 550); 25 Jul 2013 07:40:53 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 24211 invoked from network); 25 Jul 2013 07:40:53 -0000 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Xref: news.gmane.org gmane.linux.lib.musl.general:3738 Archived-At: On Thu, Jul 25, 2013 at 09:25:39AM +0200, Daniel Cegiełka wrote: > 2013/7/24 Rich Felker : > > > > > That was my question about the whole affinity system in general. My > > view is that it's stupid micro-management of scheduling that should be > > done by the kernel, and that if the kernel's not doing a good enough > > job of managing which cpu a task runs on, the kernel scheduler should > > be fixed rather than adding hacks in apps. > > Not always. Sometimes the kernel scheduler isn't the solution and you > care about isolating applications from the kernel/os. How do you do it > without this feature? > > http://highscalability.com/blog/2013/5/13/the-secret-to-10-million-concurrent-connections-the-kernel-i.html It's a nice article and I don't have data to argue with its assessment of the current bottlenecks, but I disagree with the philosophy that the solution is to bypass the kernel, in much the same way that I disagree with the philosophy (of APR, glib, gnulib, etc.) that when the libc is broken you should bypass the libc. My philosophy is that if the libc is broken, you should fix the libc, and if the kernel is broken (which it is, in many ways, especially when it comes to having too much bloated abstraction in the wrong places, not enough in the right places, and way too much need for synchronization), then you should fix the kernel. Admittedly that's not an easy task, and I should probably shut up until/unless I'm willing to do it. > musl is a very good candidate for use in HPC, so this functionality > would be very valuable. I don't disagree with that. Despite my dislike for the whole affinity system, I've deemed it important enough to be a big 1.0 roadmap item. :-) Rich