From: Trond Myklebust Subject: Re: question on sk_sem within svc_sendto Date: 30 Apr 2003 17:30:23 +0200 Sender: nfs-admin@lists.sourceforge.net Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Return-path: Received: from pat.uio.no ([129.240.130.16]) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 19AtXR-0005DF-00 for ; Wed, 30 Apr 2003 08:30:30 -0700 To: "Wendy Cheng" In-Reply-To: Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: >>>>> " " == Wendy Cheng writes: > We're in the middle of fine-tuning our linux-based file server > and currently examining the NFS zero-copy path with 2.5.x > kernel. There is a semaphore (sk_sem) within svc_sendto() that > serializes the outgoing data. Could someone shed some light and > give us an explanation why this semaphore is needed - just for > education purpose.Great thanks... You need to send one datagram at a time down each socket otherwise the client might receive data which is partially from one request, partially from another. Cheers, Trond ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs