From owner-freebsd-current Thu Apr 25 10:50:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from idiom.com (idiom.com [216.240.32.1]) by hub.freebsd.org (Postfix) with ESMTP id 6AC0537B419 for ; Thu, 25 Apr 2002 10:50:09 -0700 (PDT) Received: (from hsu@localhost) by idiom.com (8.9.3/8.9.3) id KAA55721; Thu, 25 Apr 2002 10:50:01 -0700 (PDT) Date: Thu, 25 Apr 2002 10:50:01 -0700 (PDT) From: Jeffrey Hsu Message-Id: <200204251750.KAA55721@idiom.com> To: tanimura@r.dl.itc.u-tokyo.ac.jp Subject: Re: Locking down a socket, milestone 1 Newsgroups: mgate.freebsd.current In-Reply-To: <200204241110.g3OB8u8t006194@bunko.unknown> Organization: Unknown Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <200204241110.g3OB8u8t006194@bunko.unknown> you write: >I am now working on locking down a socket. (I have heard that Jeffrey >Hsu is also doing that, but I have never seen his patch. Has anyone >seen that?) I have. :-) I do coarse-grain locking at the inpcb and sockbuf level as is done in BSD/OS. This is a lot simpler than locking down individual fields in struct socket. Are you sure we need such fine-grain locking? Jeffrey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message