From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH 1/3] Rough VJ Channel Implementation - vj_core.patch Date: Thu, 27 Apr 2006 08:41:51 +0200 Message-ID: <200604270841.52349.ak@suse.de> References: <54AD0F12E08D1541B826BE97C98F99F143AEE0@NT-SJCA-0751.brcm.ad.broadcom.com> <200604270817.36041.ak@suse.de> <20060426.232724.07687472.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: caitlinb@broadcom.com, jeff@garzik.org, kelly@au1.ibm.com, netdev@vger.kernel.org, rusty@rustcorp.com.au Return-path: Received: from mx2.suse.de ([195.135.220.15]:39383 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S964966AbWD0GmF (ORCPT ); Thu, 27 Apr 2006 02:42:05 -0400 To: "David S. Miller" In-Reply-To: <20060426.232724.07687472.davem@davemloft.net> Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thursday 27 April 2006 08:27, David S. Miller wrote: > From: Andi Kleen > Date: Thu, 27 Apr 2006 08:17:35 +0200 > > > On Thursday 27 April 2006 08:08, David S. Miller wrote: > > > > > I'm currently assuming that the protocol processing is still done in > > > the kernel on behalf of the user context, so the issues you raise > > > really aren't relevant. > > > > > > We really shouldn't be jumping the gun so far into the implementation > > > as others seem to be doing. Let's do it simple first and see if > > > putting things all the way to userspace even is necessary. > > > > I still have my doubts about doing that securely anyways. > > The NIC has a descriptor of buffers, the NIC can thus DMA right > into this buffer which only contains packet data and nothing > else outside of those packets. Yes but all clients will see all the data from all sockets don't they? [Unless you have a RDMA nic that can scale to hundred thousands of connections, but let's assume standard hardware for now] -Andi