From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id A607C87A for ; Thu, 15 Oct 2015 15:13:17 +0000 (UTC) Received: from smtprelay.hostedemail.com (smtprelay0043.hostedemail.com [216.40.44.43]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 8D5401F0 for ; Thu, 15 Oct 2015 15:13:13 +0000 (UTC) Date: Thu, 15 Oct 2015 11:13:10 -0400 From: Steven Rostedt To: Christoph Lameter Message-ID: <20151015111310.01903df1@gandalf.local.home> In-Reply-To: References: <20151013124230.1a082d28@gandalf.local.home> <20151014092041.282117ac@gandalf.local.home> <20151014112225.26771952@gandalf.local.home> <20151014143244.19c2512a@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [TECH TOPIC] Mainlining PREEMPT_RT List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 15 Oct 2015 09:22:58 -0500 (CDT) Christoph Lameter wrote: > I have no particular use case for my company in mind here. This is what I > hear when talking to various companies in a number of different areas of > computing that have tried preempt_rt. Why are they telling you this and not us? Of course this may be people that have different requirements. Need a few microsecond latencies; Try Xenomai. Need a few hundred microsecond latencies; PREEMPT_RT will do Need no interference from the kernel; Use NO_HZ_FULL Look, there's obviously users of PREEMPT_RT, so why are you trying to kill it? If anything, PREEMPT_RT has made the mainline kernel cleaner. Just because you don't see a use for it, doesn't mean one does not exist. -- Steve