From mboxrd@z Thu Jan 1 00:00:00 1970 From: Or Gerlitz Subject: Re: MLX4 Cq Question Date: Tue, 21 May 2013 18:10:56 +0300 Message-ID: <519B8E80.7040900@mellanox.com> References: <51968438.7070907@opengridcomputing.com> <519B4F81.9040108@acm.org> <519B4FEB.5090701@mellanox.com> <201305211713.24370.jackm@dev.mellanox.co.il> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201305211713.24370.jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Jack Morgenstein Cc: Bart Van Assche , Eli Cohen , Roland Dreier , Tom Tucker , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: linux-rdma@vger.kernel.org On 21/05/2013 17:13, Jack Morgenstein wrote: > I just need to verify that the patch can be applied correctly on the upstream kernel. > The use of RCU (and not spinlock) makes sense from a performance standpoint > in any case. We do NOT want to force mlx4_cq_completion to have a spinlock > which is device-global, resulting in having completion event processing be > single-threaded in effect). cool, lets do that and re-submit -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html