From owner-freebsd-smp@FreeBSD.ORG Mon Oct 18 20:17:15 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DA5116A4CE for ; Mon, 18 Oct 2004 20:17:15 +0000 (GMT) Received: from dses2.dhs.gov (dses2.dhs.gov [152.121.181.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id D173043D3F for ; Mon, 18 Oct 2004 20:17:14 +0000 (GMT) (envelope-from James.Saint-Rossy@associates.usss.dhs.gov) Received: from dhsmail2.dhs.gov by dses2.dhs.gov for freebsd-smp@freebsd.org; Mon, 18 Oct 2004 16:17:09 -0400 Received: from unknown(161.214.104.9) by dhsmail2.dhs.gov via csmap id b0068ad0_2142_11d9_8567_0002b3d786ae_31467; Mon, 18 Oct 2004 20:17:09 +0000 (UTC) Received: from [10.119.187.210] ([10.119.187.210]) by mail1.usss.dhs.gov (MOS 3.4.6-GR) with ESMTP id AOS50032; Mon, 18 Oct 2004 16:17:00 -0400 (EDT) Message-Id: <417424BC.1010502@associates.usss.dhs.gov> Date: Mon, 18 Oct 2004 16:17:00 -0400 From: "James Saint-Rossy, Thomas" User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-smp@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Status: score=0/50, host=mail1.usss.dhs.gov Subject: OpenLDAP with KSE won't run. X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 20:17:15 -0000 I've been to the openldap group and searched the newsgroups/Archives without any luck. Hopefully you guys can help me. Basically, I'm trying to get OpenLDAP to run using threads instead of as a single process. OS: 5.2.1-RELEASE FreeBSD OpenLDAP ver: openldap-server-2.2.17 (also tested with 2.2.15) I can't get slapd with syncrepl to run using KSE threads. I enabled KSE using libmap.conf. The following is end of the slapd.log with loglevel set at 255. In comparing the log to that of successful startup, without kselib, the error appears to be "daemon: select failed (22): Invalid argument". Any ideas what this means? Do I have to include threading support for db-4.2 somehow? I've also included my libmap.conf and ldd output after slapd.log. Here is the tail end of the slapd.log > Oct 14 15:25:59 ldap4 slapd[1053]: daemon: select: listen=6 > active_threads=0 tvp > =zero > Oct 14 15:25:59 ldap4 slapd[1053]: daemon: select: listen=7 > active_threads=0 tvp > =zero > Oct 14 15:25:59 ldap4 slapd[1053]: daemon: select failed (22): Invalid > argument > Oct 14 15:25:59 ldap4 slapd[1053]: daemon: abnormal condition, > shutdown initiate > d. > Oct 14 15:25:59 ldap4 slapd[1053]: daemon: closing 6 > Oct 14 15:25:59 ldap4 slapd[1053]: daemon: closing 7 > Oct 14 15:25:59 ldap4 slapd[1053]: =>do_syncrepl > Oct 14 15:25:59 ldap4 slapd[1053]: slapd shutdown: waiting for 1 > threads to term > inate > Oct 14 15:25:59 ldap4 slapd[1053]: connection_get(10) > Oct 14 15:25:59 ldap4 slapd[1053]: connection_get(10): got connid=0 > Oct 14 15:25:59 ldap4 slapd[1053]: daemon: removing 10r > Oct 14 15:25:59 ldap4 slapd[1053]: slapd shutdown: initiated > Oct 14 15:25:59 ldap4 slapd[1053]: ====> bdb_cache_release_all > Oct 14 15:25:59 ldap4 slapd[1053]: slapd shutdown: freeing system > resources. > Oct 14 15:25:59 ldap4 slapd[1053]: slapd stopped. Here's the shared libs that slapd is using. Notice that "libc_r.so.5 => /usr/lib/libkse.so.1 (0x283e9000)" > root@ldap4 /usr/local/libexec:ldd slapd > slapd: > libldap_r-2.2.so.7 => /usr/local/lib/libldap_r-2.2.so.7 > (0x28165000) > liblber-2.2.so.7 => /usr/local/lib/liblber-2.2.so.7 (0x2819f000) > libdb-4.2.so.2 => /usr/local/lib/libdb-4.2.so.2 (0x281ac000) > libssl.so.3 => /usr/local/lib/libssl.so.3 (0x28282000) > libcrypto.so.3 => /usr/local/lib/libcrypto.so.3 (0x282b3000) > libfetch.so.3 => /usr/lib/libfetch.so.3 (0x283b9000) > libcom_err.so.2 => /usr/lib/libcom_err.so.2 (0x283c6000) > libcrypt.so.2 => /lib/libcrypt.so.2 (0x283c8000) > libwrap.so.3 => /usr/lib/libwrap.so.3 (0x283e1000) > libc_r.so.5 => /usr/lib/libkse.so.1 (0x283e9000) > libc.so.5 => /lib/libc.so.5 (0x2840d000) > libsasl2.so.2 => /usr/local/lib/libsasl2.so.2 (0x284e7000) > libssl.so.3 => /usr/lib/libssl.so.3 (0x284fd000) > libcrypto.so.3 => /lib/libcrypto.so.3 (0x2852f000) Here is my libmap.conf. In addition I've also tried a test making libkse the system default with the same results. > # /etc/libmap.conf > # > # candidate mapping > # > libc_r.so.5 libthr.so.1 # Everything uses 'libthr' > libc_r.so libthr.so > > [/usr/local/libexec/slapd] > libc_r.so.5 libkse.so.1 > libc_r.so libkse.so > > [slapd] > libc_r.so.5 libkse.so.1 > libc_r.so libk Thanks for any assistance, James. From owner-freebsd-smp@FreeBSD.ORG Mon Oct 18 20:25:29 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4615016A4CE for ; Mon, 18 Oct 2004 20:25:29 +0000 (GMT) Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 584D143D1F for ; Mon, 18 Oct 2004 20:25:28 +0000 (GMT) (envelope-from Venkatesh.Babu@nokia.com) Received: from esdks001.ntc.nokia.com (esdks001.ntc.nokia.com [172.21.138.120])i9IKPQh17170 for ; Mon, 18 Oct 2004 23:25:26 +0300 (EET DST) X-Scanned: Mon, 18 Oct 2004 23:24:52 +0300 Nokia Message Protector V1.3.31 2004060815 - RELEASE Received: (from root@localhost) by esdks001.ntc.nokia.com (8.12.9/8.12.9) id i9IKOqQP023097 for ; Mon, 18 Oct 2004 23:24:52 +0300 Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks001.ntc.nokia.com 00oASen5; Mon, 18 Oct 2004 23:24:51 EEST Received: from daebh002.NOE.Nokia.com (daebh002.americas.nokia.com [10.241.35.122])i9IKOjS28971 for ; Mon, 18 Oct 2004 23:24:45 +0300 (EET DST) Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh002.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Mon, 18 Oct 2004 15:24:31 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Mon, 18 Oct 2004 13:24:30 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Multiprocessing for network protocol stack Thread-Index: AcSzhGcKpgAWHaDDTYqSh0hin+XNfwBy8ePw From: To: X-OriginalArrivalTime: 18 Oct 2004 20:24:31.0851 (UTC) FILETIME=[79CA03B0:01C4B550] cc: Venkatesh.Babu@nokia.com Subject: Multiprocessing for network protocol stack X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 20:25:29 -0000 We have a proprietary OS, which is a variant of FreeBSD 2.x and has extensive changes to protocol stack. We are planning to migrate to the latest FreeBSD like 4.x or 5.x to get multiprocessor support. So I am trying to evaluate these options. How good the network protocol stack takes advantages of the multi processor in 5.x ? What parallelizing paradigm (Connection level parallelism / Packet = level parallelism / processor per message / predictable parallel protocol processing) is implemented for network protocol stack (like TCP/IP) in BSD 5.x ? Are there any benchmarks on the performance analysis of network = protocol stack on multiprocessor system ? Thanks, VBabu From owner-freebsd-smp@FreeBSD.ORG Mon Oct 18 21:27:32 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E501016A4CE for ; Mon, 18 Oct 2004 21:27:32 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABC6843D41 for ; Mon, 18 Oct 2004 21:27:30 +0000 (GMT) (envelope-from john@baldwin.cx) Received: (qmail 27457 invoked from network); 18 Oct 2004 21:27:30 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 18 Oct 2004 21:27:30 -0000 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i9ILRQuG041581 for ; Mon, 18 Oct 2004 17:27:26 -0400 (EDT) (envelope-from john@baldwin.cx) Received: from zion.baldwin.cx (localhost [127.0.0.1]) by zion.baldwin.cx (8.12.10/8.12.10) with ESMTP id i9ILRQ8h000375 for ; Mon, 18 Oct 2004 17:27:26 -0400 (EDT) (envelope-from john@zion.baldwin.cx) Received: from localhost (localhost [[UNIX: localhost]]) by zion.baldwin.cx (8.12.10/8.12.10/Submit) id i9ILRQWB000374 for freebsd-smp@freebsd.org; Mon, 18 Oct 2004 17:27:26 -0400 (EDT) (envelope-from john) From: John Baldwin To: freebsd-smp@freebsd.org Date: Mon, 18 Oct 2004 17:23:20 -0400 User-Agent: KMail/1.6 References: <20041015122943.GA29434@hysteria.sk> In-Reply-To: <20041015122943.GA29434@hysteria.sk> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200410181723.21265.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: smp problem with 8 CPU's X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 21:27:33 -0000 On Friday 15 October 2004 08:29 am, rejden wrote: > Hi, > i cannot get working smp on compaq proliant dl760 with 8cpu's xeon 700mhz > > southpole# uname -a > FreeBSD southpole.brc.cpqcorp.net 5.3-BETA7 FreeBSD 5.3-BETA7 #0: Fri Jan > 31 05:24:02 CET 2003 > root@southpole.brc.cpqcorp.net:/usr/obj/usr/src/sys/SOUTHPOLE i386 > > southpole# dmesg > Copyright (c) 1992-2004 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.3-BETA7 #0: Fri Jan 31 05:24:02 CET 2003 > root@southpole.brc.cpqcorp.net:/usr/obj/usr/src/sys/SOUTHPOLE > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel Pentium III Xeon (700.01-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x6a4 Stepping = 4 > > Features=0x383f9ff,PAT,PSE36,MMX,FXSR,SSE> real memory = 2147450880 (2047 MB) > avail memory = 2095992832 (1998 MB) > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard Try disabling ACPI. This looks to be an older machine and the BIOS might not have an MADT table which is ACPI's equivalent to the MP Table (sort of). -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-smp@FreeBSD.ORG Mon Oct 18 21:30:26 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 653A616A4D1 for ; Mon, 18 Oct 2004 21:30:26 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C39B43D41 for ; Mon, 18 Oct 2004 21:30:26 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A451D521A6; Mon, 18 Oct 2004 14:30:32 -0700 (PDT) Date: Mon, 18 Oct 2004 14:30:32 -0700 From: Kris Kennaway To: "James Saint-Rossy, Thomas" Message-ID: <20041018213032.GA61682@xor.obsecurity.org> References: <417424BC.1010502@associates.usss.dhs.gov> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Q68bSM7Ycu6FN28Q" Content-Disposition: inline In-Reply-To: <417424BC.1010502@associates.usss.dhs.gov> User-Agent: Mutt/1.4.2.1i cc: freebsd-smp@freebsd.org Subject: Re: OpenLDAP with KSE won't run. X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 21:30:26 -0000 --Q68bSM7Ycu6FN28Q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Oct 18, 2004 at 04:17:00PM -0400, James Saint-Rossy, Thomas wrote: > I've been to the openldap group and searched the newsgroups/Archives=20 > without any luck. Hopefully you guys can help me. Basically, I'm=20 > trying to get OpenLDAP to run using threads instead of as a single proces= s. >=20 > OS: 5.2.1-RELEASE FreeBSD > OpenLDAP ver: openldap-server-2.2.17 (also tested with 2.2.15) >=20 > I can't get slapd with syncrepl to run using KSE threads. I enabled KSE= =20 > using libmap.conf. The following is end of the slapd.log with loglevel= =20 > set at 255. In comparing the log to that of successful startup, without= =20 > kselib, the error appears to be "daemon: select failed (22): Invalid=20 > argument". Any ideas what this means? Do I have to include threading=20 > support for db-4.2 somehow? I've also included my libmap.conf and ldd=20 > output after slapd.log. Try updating to 5.3; 5.2.1 had lots of bugs that were later fixed. Kris --Q68bSM7Ycu6FN28Q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBdDX4Wry0BWjoQKURAnVzAJ4phz6jm5CWOEr117WYCBkAyMRALwCg7RBX K8begUTZNhHbmKec1v2h5Jo= =yyfH -----END PGP SIGNATURE----- --Q68bSM7Ycu6FN28Q-- From owner-freebsd-smp@FreeBSD.ORG Tue Oct 19 01:33:40 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A66C116A4CE for ; Tue, 19 Oct 2004 01:33:40 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4436343D31 for ; Tue, 19 Oct 2004 01:33:35 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by mproxy.gmail.com with SMTP id 74so273218rnk for ; Mon, 18 Oct 2004 18:33:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=nSrJL0OWhHyPCXvKbgkfGEdwYBhdsjH27JzPPQhSaRlgaHMeJZMEmKHKhcZYitSQpuOhqIJAu2QGekSoDgX2dFqrwVLk1ePCH12XRDl0fLosDxEyyafwAvHSuTu6SfI/CkEBZODbgs3k37WVqep0kZFLgpbjXYkX6Kxbv7GqeKE Received: by 10.38.72.80 with SMTP id u80mr1710622rna; Mon, 18 Oct 2004 18:33:14 -0700 (PDT) Received: by 10.38.13.37 with HTTP; Mon, 18 Oct 2004 18:33:14 -0700 (PDT) Message-ID: <84dead72041018183348829ff1@mail.gmail.com> Date: Tue, 19 Oct 2004 01:33:14 +0000 From: Joseph Koshy To: "venkatesh.babu@nokia.com" In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: cc: freebsd-smp@freebsd.org Subject: Re: Multiprocessing for network protocol stack X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 01:33:40 -0000 > latest FreeBSD like 4.x or 5.x to get multiprocessor support. So I am > trying to evaluate these options. You must have already looked at the following presentation (it gives a good overview of the stuff in 5.x): http://people.freebsd.org/~andre/FreeBSD-5.3-Networking.pdf > What parallelizing paradigm (Connection level parallelism / Packet level > parallelism / processor per message / predictable parallel protocol > processing) is implemented for network protocol stack (like TCP/IP) in > BSD 5.x ? What is "predictable parallel protocol processing"? From owner-freebsd-smp@FreeBSD.ORG Tue Oct 19 16:09:15 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 329F416A4CE for ; Tue, 19 Oct 2004 16:09:15 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB33843D41 for ; Tue, 19 Oct 2004 16:09:14 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by mproxy.gmail.com with SMTP id 74so341087rnk for ; Tue, 19 Oct 2004 09:09:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=q2rMBz4LQIsjU/h22lccggclTSYNH4ilzJ3xhZ3uJD+47WhxMQVm2+cnQ15NY0TrpsVE9FBfojW//DaHPVpO0fZf3pUgQ5snAmVdv3EsdlcGrCgWXpZVVInwo1HtKiUuhnOnBCt6LmYvw0E4yAMLoTkmr9oQyXax1ocI8f4qaUU Received: by 10.38.152.46 with SMTP id z46mr90790rnd; Tue, 19 Oct 2004 09:09:14 -0700 (PDT) Received: by 10.38.13.37 with HTTP; Tue, 19 Oct 2004 09:09:14 -0700 (PDT) Message-ID: <84dead7204101909093c3a6f27@mail.gmail.com> Date: Tue, 19 Oct 2004 21:39:14 +0530 From: Joseph Koshy To: John Baldwin In-Reply-To: <200410141441.56479.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <84dead7204101320022bd6602e@mail.gmail.com> <200410141441.56479.jhb@FreeBSD.org> cc: freebsd-smp@freebsd.org Subject: Re: Moving a kthread between CPUs? X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joseph Koshy List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 16:09:15 -0000 > In 5.x there's a sched_bind() interface that can be used to pin a thread to an > arbitrary CPU. sched_bind() could work. Thanks. A quick grep didn't reveal any uses of sched_{bind,unbind} inside the kernel though ... From owner-freebsd-smp@FreeBSD.ORG Tue Oct 19 19:00:15 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5294316A4CF for ; Tue, 19 Oct 2004 19:00:15 +0000 (GMT) Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EF3943D3F for ; Tue, 19 Oct 2004 19:00:12 +0000 (GMT) (envelope-from Venkatesh.Babu@nokia.com) Received: from esdks002.ntc.nokia.com (esdks002.ntc.nokia.com [172.21.138.121])i9JJ08W23660; Tue, 19 Oct 2004 22:00:08 +0300 (EET DST) X-Scanned: Tue, 19 Oct 2004 21:59:48 +0300 Nokia Message Protector V1.3.31 2004060815 - RELEASE Received: (from root@localhost) by esdks002.ntc.nokia.com (8.12.9/8.12.9) id i9JIxmWW019915; Tue, 19 Oct 2004 21:59:48 +0300 Received: from mgw-int2.ntc.nokia.com (172.21.143.97) by esdks002.ntc.nokia.com 00VzbgdD; Tue, 19 Oct 2004 21:59:48 EEST Received: from daebh001.NOE.Nokia.com (daebh001.americas.nokia.com [10.241.35.121])i9JIxlS09709; Tue, 19 Oct 2004 21:59:47 +0300 (EET DST) Received: from mvebe001.NOE.Nokia.com ([172.18.140.37]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6881); Tue, 19 Oct 2004 13:57:26 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Tue, 19 Oct 2004 11:57:26 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Multiprocessing for network protocol stack Thread-Index: AcS1e9T+H0MbN2bCSC2Xb+6ge09X4wAj7zcw From: To: X-OriginalArrivalTime: 19 Oct 2004 18:57:26.0587 (UTC) FILETIME=[79B3C0B0:01C4B60D] cc: freebsd-smp@freebsd.org Subject: RE: Multiprocessing for network protocol stack X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 19:00:15 -0000 I looked at the following document, it gives the overview of the 5.x changes but it has little information on parallelizing the protocol stack. There are only 3 sentences and which says different concepts like per-CPU split of packets and connections are used. I am looking for more details. "Predictable Parallel Protocol Processing" paradigm is useful in cases where predictable delay is of importance. Typically useful for the = applications like video-on-demand, distributed multi-player games and = video conferences. For more information refer the following paper - http://www.artes.uu.se/project/P2-9805.pdf VBabu -----Original Message----- From: owner-freebsd-smp@freebsd.org [mailto:owner-freebsd-smp@freebsd.org]On Behalf Of ext Joseph Koshy Sent: Monday, October 18, 2004 6:33 PM To: Babu Venkatesh (Nokia-NET/MtView) Cc: freebsd-smp@freebsd.org Subject: Re: Multiprocessing for network protocol stack > latest FreeBSD like 4.x or 5.x to get multiprocessor support. So I am > trying to evaluate these options. You must have already looked at the following presentation (it gives a good overview of the stuff in 5.x): http://people.freebsd.org/~andre/FreeBSD-5.3-Networking.pdf > What parallelizing paradigm (Connection level parallelism / Packet = level > parallelism / processor per message / predictable parallel protocol > processing) is implemented for network protocol stack (like TCP/IP) in > BSD 5.x ? What is "predictable parallel protocol processing"? _______________________________________________ freebsd-smp@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-smp To unsubscribe, send any mail to "freebsd-smp-unsubscribe@freebsd.org" From owner-freebsd-smp@FreeBSD.ORG Tue Oct 19 20:02:42 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C31616A55F for ; Tue, 19 Oct 2004 20:02:42 +0000 (GMT) Received: from onyx.hysteria.sk (onyx.hysteria.sk [195.168.3.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D17043D53 for ; Tue, 19 Oct 2004 20:02:41 +0000 (GMT) (envelope-from rejden@hysteria.sk) Received: (qmail 28327 invoked by uid 1607); 19 Oct 2004 20:02:34 -0000 Date: Tue, 19 Oct 2004 22:02:34 +0200 From: rejden To: Gavin Atkinson Message-ID: <20041019200234.GA27619@hysteria.sk> References: <20041015122943.GA29434@hysteria.sk> <1097848525.28609.35.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1097848525.28609.35.camel@buffy.york.ac.uk> User-Agent: Mutt/1.4.2i X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on onyx.hysteria.sk X-Spam-Status: No, hits=-4.9 required=5.0 cc: freebsd-current@freebsd.org cc: freebsd-smp@freebsd.org Subject: Re: smp problem with 8 CPU's X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 20:02:42 -0000 On Fri, Oct 15, 2004 at 02:55:25PM +0100, Gavin Atkinson wrote: > On Fri, 2004-10-15 at 13:29, rejden wrote: > > Hi, > > i cannot get working smp on compaq proliant dl760 with 8cpu's xeon 700mhz > > > > southpole# uname -a > > FreeBSD southpole.brc.cpqcorp.net 5.3-BETA7 FreeBSD 5.3-BETA7 #0: Fri Jan 31 05:24:02 CET 2003 root@southpole.brc.cpqcorp.net:/usr/obj/usr/src/sys/SOUTHPOLE i386 > > Are you sure you have SMP compiled into your kernel? and the apic > device? A verbose dmesg would probably be a lot more use.... > > Gavin > So guys i finaly solve it, i'm really sorry for bothering you becouse it was really compaq proliant bios who decited to use hardware profile which permit only one CPU :) So i enable whole 8cpu's thanks for cooperation rejden From owner-freebsd-smp@FreeBSD.ORG Tue Oct 19 20:41:23 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BE1216A4CE for ; Tue, 19 Oct 2004 20:41:23 +0000 (GMT) Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C38A43D49 for ; Tue, 19 Oct 2004 20:41:23 +0000 (GMT) (envelope-from julian@elischer.org) Received: from elischer.org (julian.vicor-nb.com [208.206.78.97]) by mail.vicor-nb.com (Postfix) with ESMTP id 3411D7A427; Tue, 19 Oct 2004 13:41:23 -0700 (PDT) Message-ID: <41757BF3.8030005@elischer.org> Date: Tue, 19 Oct 2004 13:41:23 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516 X-Accept-Language: en, hu MIME-Version: 1.0 To: Venkatesh.Babu@nokia.com References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-smp@freebsd.org cc: joseph.koshy@gmail.com Subject: Re: Multiprocessing for network protocol stack X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Oct 2004 20:41:23 -0000 Venkatesh.Babu@nokia.com wrote: > I looked at the following document, it gives the overview of the 5.x >changes but it has little information on parallelizing the protocol >stack. There are only 3 sentences and which says different concepts like >per-CPU split of packets and connections are used. I am looking for more >details. > > "Predictable Parallel Protocol Processing" paradigm is useful in >cases where predictable delay is of importance. Typically useful for the applications like video-on-demand, distributed multi-player games and video conferences. For more information refer the following paper - >http://www.artes.uu.se/project/P2-9805.pdf > Ah he's talking about protocol specific maximum bounded latency.. :-) > > VBabu > > > From owner-freebsd-smp@FreeBSD.ORG Wed Oct 20 01:06:49 2004 Return-Path: Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 632C816A4CE for ; Wed, 20 Oct 2004 01:06:49 +0000 (GMT) Received: from dses1.dhs.gov (dses1.dhs.gov [152.121.181.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FB4A43D31 for ; Wed, 20 Oct 2004 01:06:48 +0000 (GMT) (envelope-from James.Saint-Rossy@associates.usss.dhs.gov) Received: from dhsmail1.dhs.gov by dses1.dhs.gov; Tue, 19 Oct 2004 21:06:47 -0400 Received: from unknown(161.214.104.9) by dhsmail1.dhs.gov via csmap id 507c1f38_2234_11d9_9777_0002b3a82863_14289; Wed, 20 Oct 2004 01:06:47 +0000 (UTC) Received: from [10.119.187.210] ([10.119.187.210]) by mail1.usss.dhs.gov (MOS 3.4.6-GR) with ESMTP id AOW58464; Tue, 19 Oct 2004 21:06:43 -0400 (EDT) Message-Id: <4175BA23.7080209@associates.usss.dhs.gov> Date: Tue, 19 Oct 2004 21:06:43 -0400 From: "James Saint-Rossy, Thomas" User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-smp@freebsd.org References: <417424BC.1010502@associates.usss.dhs.gov> <20041018213032.GA61682@xor.obsecurity.org> In-Reply-To: <20041018213032.GA61682@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Junkmail-Status: score=0/50, host=mail1.usss.dhs.gov cc: Kris Kennaway Subject: Re: OpenLDAP with KSE won't run. X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2004 01:06:49 -0000 That seems to be it. Openldap now appears to start and run normally using threads. I don't even need to specify the kse lib using libmap.conf. Thanks, James. Kris Kennaway wrote: >On Mon, Oct 18, 2004 at 04:17:00PM -0400, James Saint-Rossy, Thomas wrote: > > >>I've been to the openldap group and searched the newsgroups/Archives >>without any luck. Hopefully you guys can help me. Basically, I'm >>trying to get OpenLDAP to run using threads instead of as a single process. >> >>OS: 5.2.1-RELEASE FreeBSD >>OpenLDAP ver: openldap-server-2.2.17 (also tested with 2.2.15) >> >>I can't get slapd with syncrepl to run using KSE threads. I enabled KSE >>using libmap.conf. The following is end of the slapd.log with loglevel >>set at 255. In comparing the log to that of successful startup, without >>kselib, the error appears to be "daemon: select failed (22): Invalid >>argument". Any ideas what this means? Do I have to include threading >>support for db-4.2 somehow? I've also included my libmap.conf and ldd >>output after slapd.log. >> >> > >Try updating to 5.3; 5.2.1 had lots of bugs that were later fixed. > >Kris > >