From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [RFC] act_cpu: redirect skb receiving to a special CPU. Date: Sat, 05 Jun 2010 17:00:15 +0200 Message-ID: <1275750015.5238.249.camel@edumazet-laptop> References: <1275743224.3490.44.camel@bigi> <1275746045.3490.60.camel@bigi> <1275748004.3490.86.camel@bigi> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Changli Gao , "David S. Miller" , Tom Herbert , Linux Netdev List To: hadi@cyberus.ca Return-path: Received: from mail-wy0-f174.google.com ([74.125.82.174]:60430 "EHLO mail-wy0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933319Ab0FEPAU (ORCPT ); Sat, 5 Jun 2010 11:00:20 -0400 Received: by wyi11 with SMTP id 11so1489933wyi.19 for ; Sat, 05 Jun 2010 08:00:19 -0700 (PDT) In-Reply-To: <1275748004.3490.86.camel@bigi> Sender: netdev-owner@vger.kernel.org List-ID: Le samedi 05 juin 2010 =C3=A0 10:26 -0400, jamal a =C3=A9crit : > Indeed it is AMD specific - but my view is if i was using AMD that wo= uld > be more efficient way of doing it; i.e IPI is the lowest common > denominator which works on all archs. Essentially what i am saying is > this would be a "inter-cpu messaging netdev" and i could replace its > send/recv parts from what we do in the RPS path right now to one that > uses AMD hypertransport etc. You do realize this should be discussed on lkml , of course ?