From owner-freebsd-arch Thu Nov 30 23:22:45 2000 Delivered-To: freebsd-arch@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id E129537B400; Thu, 30 Nov 2000 23:22:38 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA11231; Fri, 1 Dec 2000 00:22:35 -0700 (MST) (envelope-from ken) Date: Fri, 1 Dec 2000 00:22:35 -0700 From: "Kenneth D. Merry" To: Bosko Milekic Cc: Andrew Gallatin , arch@FreeBSD.ORG, alfred@FreeBSD.ORG Subject: Re: zero copy code review Message-ID: <20001201002235.D10772@panzer.kdm.org> References: <14886.63486.157224.937225@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from bmilekic@technokratis.com on Thu, Nov 30, 2000 at 10:18:43PM -0500 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 30, 2000 at 22:18:43 -0500, Bosko Milekic wrote: > On Thu, 30 Nov 2000, Andrew Gallatin wrote: > > [...] > > <... some helpful comments deleted ....> > > > > Many of your comments are directly related to -current, I > > think I'll let Ken address them... > > Another one directly related to -CURRENT: > > I just noticed that the uipc_jumbo.c stuff does not do any locking. > Perhaps it would be nice to lock the code sooner or later. I would be > willing to go over it and do it but, as I said, I am really not going to > be able to do much until 2 weeks from now. It does have spls in the right places, in this case splimp() and splvm(). Would you just convert those to the proper mutexes, or are we going to go with per-data-structure mutexes (i.e. a little finer granularity), or...? (I don't know much about the mutex strategy we're using...) > Furthermore, I wonder if Alfred is gutsy enough ( :-) ) to raise his > voice and let us know how much this may interefere with the adding of > locks to sockets in the uipc subsystem, and possibly the stack as well. > Alfred, where are the potential problems? (As you've already written a > portion of the latter, I assume you're very well aware)... Hopefully it won't cause many problems.. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message