From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754050AbaEUXXX (ORCPT ); Wed, 21 May 2014 19:23:23 -0400 Received: from one.firstfloor.org ([193.170.194.197]:58795 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754025AbaEUXXU (ORCPT ); Wed, 21 May 2014 19:23:20 -0400 Date: Thu, 22 May 2014 01:23:18 +0200 From: Andi Kleen To: Linus Torvalds Cc: Andi Kleen , Andy Lutomirski , Steven Rostedt , "linux-kernel@vger.kernel.org" , "H. Peter Anvin" , Ingo Molnar , Thomas Gleixner , Borislav Petkov Subject: Re: [RFC] x86_64: A real proposal for iret-less return to kernel Message-ID: <20140521232318.GP1873@two.firstfloor.org> References: <20140521222541.GO1873@two.firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Hardware-interrupts during kernel are actually fairly common under > network-intensive loads, even outside of idle (but idle is admittedly > likely *the* most common one). Many network loads are fairly > kernel-intensive. For network workloads we can arbitarily coalesce interrupts or just use NAPI to lower the costs. No need to optimize network interrupts too much. -Andi