From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 22 00:49:46 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA032106566B for ; Sun, 22 Feb 2009 00:49:46 +0000 (UTC) (envelope-from gerryw@compvia.com) Received: from omr1.networksolutionsemail.com (omr1.networksolutionsemail.com [205.178.146.51]) by mx1.freebsd.org (Postfix) with ESMTP id 52C078FC14 for ; Sun, 22 Feb 2009 00:49:46 +0000 (UTC) (envelope-from gerryw@compvia.com) Received: from mail.networksolutionsemail.com (ns-omr1.mgt.netsol.com [10.49.6.64]) by omr1.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id n1M0YhSr023849 for ; Sat, 21 Feb 2009 19:34:43 -0500 Received: (qmail 10267 invoked by uid 78); 22 Feb 2009 00:34:43 -0000 Received: from unknown (HELO ?10.10.20.102?) (sales@compvia.com@72.177.99.161) by ns-omr1.lb.hosting.dc2.netsol.com with SMTP; 22 Feb 2009 00:34:43 -0000 Message-Id: <8AC3EBEC-71C1-4E29-9E20-680AF49626BF@compvia.com> From: Gerry Weaver To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sat, 21 Feb 2009 18:34:42 -0600 X-Mailer: Apple Mail (2.930.3) Subject: variable args in kernel module? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2009 00:49:47 -0000 Hello All, How does one make use of variable arguments in a kernel module? It seems doable ala printf etc. I want to front end sprintf to calculate buffer size. I've been looking through the source tree, but no luck as of yet. Thanks, Gerry From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 22 07:00:49 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD0B1106564A for ; Sun, 22 Feb 2009 07:00:49 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outU.internet-mail-service.net (outu.internet-mail-service.net [216.240.47.244]) by mx1.freebsd.org (Postfix) with ESMTP id 956BC8FC0C for ; Sun, 22 Feb 2009 07:00:49 +0000 (UTC) (envelope-from julian@elischer.org) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 447C32428 for ; Sat, 21 Feb 2009 22:49:35 -0800 (PST) X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id BF6C62D6017 for ; Sat, 21 Feb 2009 22:49:34 -0800 (PST) Message-ID: <49A0F57E.2030506@elischer.org> Date: Sat, 21 Feb 2009 22:49:34 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: hackers@freebsd.org References: <20090213115426.GA15211@holyman.cobbled.net> In-Reply-To: <20090213115426.GA15211@holyman.cobbled.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: removal of NGROUPS_MAX dependancy from base X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2009 07:00:49 -0000 ttw+bsd@cobbled.net wrote: > attached is the first in a series of patches that is intended to > remove the current limitation on group membership. > > this patch should remove the dependancy on the definition of > NGROUPS_MAX as a static constant and implement it as a writable > sysconf variable of the same. it should also make the necessary > changes to the codebase to support those. > > i need some guidance as to what i should re-define NGROUPS_MAX to be > (so that code that depends on it can continue to operate, i'm thinking > just make it 16 but perhaps it would be worth extending the default > while we're at it to something like 64??). i also need feedback on > any braindamage in the current changes. > > the next step will be to extend the kernel groups and map them back > to the user structs / calls. finally i'll extend the user groups > and implement those calls. > > nb: not tested the code (it builds) ... was intending to test it on > my XEN box but only just realised that Xen on amd64 isn't working. > :-( > > happy for any questions that may help guide the process. What do you do about NFS? I seem to remember that NFWS had a maximum number of groups supported.. > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 22 07:22:32 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32F8F1065670 for ; Sun, 22 Feb 2009 07:22:32 +0000 (UTC) (envelope-from gerryw@compvia.com) Received: from omr4.networksolutionsemail.com (omr4.networksolutionsemail.com [205.178.146.54]) by mx1.freebsd.org (Postfix) with ESMTP id E98398FC12 for ; Sun, 22 Feb 2009 07:22:31 +0000 (UTC) (envelope-from gerryw@compvia.com) Received: from mail.networksolutionsemail.com (ns-omr4.mgt.netsol.com [10.49.6.67]) by omr4.networksolutionsemail.com (8.13.6/8.13.6) with SMTP id n1M7MUr2003512 for ; Sun, 22 Feb 2009 02:22:31 -0500 Received: (qmail 28647 invoked by uid 78); 22 Feb 2009 07:22:30 -0000 Received: from unknown (HELO ?10.10.20.102?) (sales@compvia.com@72.177.99.161) by ns-omr4.lb.hosting.dc2.netsol.com with SMTP; 22 Feb 2009 07:22:30 -0000 Message-Id: <0C6BEA08-70DC-451D-AA87-885748574100@compvia.com> From: Gerry Weaver To: freebsd-hackers@freebsd.org In-Reply-To: <8AC3EBEC-71C1-4E29-9E20-680AF49626BF@compvia.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sun, 22 Feb 2009 01:22:29 -0600 References: <8AC3EBEC-71C1-4E29-9E20-680AF49626BF@compvia.com> X-Mailer: Apple Mail (2.930.3) Subject: Re: variable args in kernel module? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2009 07:22:32 -0000 Hello All, Solved. I found machine/stdarg.h. Thanks, Gerry On Feb 21, 2009, at 6:34 PM, Gerry Weaver wrote: > Hello All, > > How does one make use of variable arguments in a kernel module? It > seems doable ala printf etc. I want to front end sprintf to > calculate buffer size. I've been looking through the source tree, > but no luck as of yet. > > Thanks, > Gerry > > > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org > " > From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 22 11:41:56 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A617D106566B for ; Sun, 22 Feb 2009 11:41:56 +0000 (UTC) (envelope-from fergus@cobbled.net) Received: from mail1.slb.deg.dub.stisp.net (mail1.slb.deg.dub.stisp.net [84.203.253.98]) by mx1.freebsd.org (Postfix) with SMTP id DB4BD8FC19 for ; Sun, 22 Feb 2009 11:41:55 +0000 (UTC) (envelope-from fergus@cobbled.net) Received: (qmail 90421 invoked from network); 22 Feb 2009 11:41:53 -0000 Received: from unknown (HELO holyman.cobbled.net) (84.203.180.117) by mail1.slb.deg.dub.stisp.net with SMTP; 22 Feb 2009 11:41:53 -0000 Received: by holyman.cobbled.net (Postfix, from userid 16385) id A739A1031D; Sun, 22 Feb 2009 11:41:53 +0000 (UTC) Date: Sun, 22 Feb 2009 11:07:19 +0000 From: ttw+bsd@cobbled.net To: Julian Elischer Message-ID: <20090222110719.GA16634@holyman.cobbled.net> References: <20090213115426.GA15211@holyman.cobbled.net> <49A0F57E.2030506@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49A0F57E.2030506@elischer.org> Resent-From: fergus@cobbled.net Resent-Date: Sun, 22 Feb 2009 11:41:53 +0000 Resent-To: hackers@freebsd.org Resent-Message-Id: <20090222114153.A739A1031D@holyman.cobbled.net> Cc: Subject: Re: removal of NGROUPS_MAX dependancy from base X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2009 11:41:56 -0000 On 21.02-22:49, Julian Elischer wrote: [ ... ] > >this patch should remove the dependancy on the definition of > >NGROUPS_MAX as a static constant and implement it as a writable > >sysconf variable of the same. it should also make the necessary > >changes to the codebase to support those. [ ... ] > What do you do about NFS? > I seem to remember that NFWS had a maximum number of groups supported.. NFS will be supported by mapping 16 groups into the auth_unix structure dynamically. my intention is to try and make this transparent by allocating moving the 'most used' groups into that mapping as user processes check them, however, this is very conceptual at the moment and needs more thought as well as validation from others with more experience. From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 22 17:15:57 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32C2A1065673 for ; Sun, 22 Feb 2009 17:15:57 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mx1.freebsd.org (Postfix) with ESMTP id B82998FC0C for ; Sun, 22 Feb 2009 17:15:56 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by ey-out-2122.google.com with SMTP id d26so223684eyd.7 for ; Sun, 22 Feb 2009 09:15:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EsIMAyOiybveveCposo7jbTYlLpm0zOjLHecMl3CtsM=; b=egvBJS4/eCu2Q9z/UQdDn2EhspSK0vlKr1tDbED5tGlwEexrijm/i6RCm41FZEPUhj cWn1XVBAKz/0+a6JkqtktxM3MwN+epuRiExMz3wVNz4/kH1erDciSYsgHXGVflvg0hKH Dt+iw95lsTCUITN9PYmKUB5wML+hp75FJZd5E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ICC1NXx6wRoqW+1QFkjnXmEfKwJpk1xt1PvZBnkQWBghGhYedLytHnRYmA/0LMgVCf 5Jvk5oXLxcOEpcsZQYAbl0eiCF+0NgW+H2Gq//biAYkTsH3ipeozQ7xCmrl6IavNWsQr o9xH6YQfiZxFuXMuUn/TwbFkUku3jzflYKYp8= MIME-Version: 1.0 Received: by 10.210.57.5 with SMTP id f5mr2685357eba.14.1235322955690; Sun, 22 Feb 2009 09:15:55 -0800 (PST) In-Reply-To: <20090221015518.GA44336@michelle.cdnetworks.co.kr> References: <1bd550a00902200825w3f225d0at99cfd1c6bb63ea0@mail.gmail.com> <20090221015518.GA44336@michelle.cdnetworks.co.kr> Date: Sun, 22 Feb 2009 18:15:55 +0100 Message-ID: <1bd550a00902220915p276b8b61m4b757373a443348a@mail.gmail.com> From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: pyunyh@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers Subject: Re: FBSD 7.0-p3 NIC driver problem (Realtek) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2009 17:15:57 -0000 On Sat, Feb 21, 2009 at 2:55 AM, Pyun YongHyeon wrote: > On Fri, Feb 20, 2009 at 05:25:26PM +0100, Fernando Apestegu?a wrote: >> Hi all, >> >> I copy here the mail I sent to freebsd-questions cause I didn't get any answers: >> >> >> Yesterday I updated to 7.1-p3 on AMD64 arch. >> >> Since then, the NIC is not detected anymore. ifconfig doesn't show it >> and I can't connect to the Internet. >> >> There were well-known issues with this NIC model before, >> (http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-11/msg00299.html) >> but the weird thing is that it seemed to be fine with >> 7.1-RELEASE and newer till this -p3. >> >> It doesn't recognize the card in 4/5 boot sequences (really annoying). >> >> Anybody with this problem? > > I'm not sure you're suffering from MAC power saving issue of > RealTek PCIe controller. Sometimes re(4) used to fail to wakeup the > controller which in turn resulted in 'no driver' for the > controller. If this is the case you can see "MII without any phy!" > message in dmesg output. You are right, I see that message. > r188358(cvs if_re.c 1.95.2.40) should fix the issue so please try > latest 7-stable or copy if_re.c, if_rlreg.h and if_rl.c from HEAD/ > 7-stable to your 7.1-RELEASE box and rebuild kernel. > If you still see the same issue please let me know. I copied the files and restarted my computer 5 times and the NIC was present in all of them. I will watch this issue and I will let you know if I notice more problems. Thanks so much for your help. > > Btw, stable@ is more appropriate list for this type of issues. Even if I'm not using -STABLE? Cheers. > > From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 23 00:19:47 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B32711065679 for ; Mon, 23 Feb 2009 00:19:47 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.186]) by mx1.freebsd.org (Postfix) with ESMTP id 481F68FC17 for ; Mon, 23 Feb 2009 00:19:47 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by ti-out-0910.google.com with SMTP id a1so1168246tib.3 for ; Sun, 22 Feb 2009 16:19:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=8bKWNY59tqUguQlvBYUJm4jskL79rIkgxC9U6HS6WUY=; b=nQr6EMEs04iJ5MhFasDnvCP5b77TFxB+C7QKujMx97vVYozF/xTOOu0qdw5DgTDVO0 xZqpAHBBN4OAKNfahMPlS5TYsiuDeqiTewpXIknwsyWpX6abDlRqO8mNrHtrns/QaZ1w FIi8tAuyKkaIv7vta2DUyqi6mh1tFXEQH4EBY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=kMHG7VjASTOkgjv7oMIR7BiB5eIlGvfG38hZHbuHrSFYptqnSiYfiTkfqMjQVCK5mW WSZ8DaelfCqCJhWbTTgXXg5+NYCfWq+Xj3R5iK2//d2rW7IZpGGTpQ26vP7CVxWgTrOZ MxeunJ/gj7U2shSOOCXmr97OvIFKfzSgg9jeA= Received: by 10.110.103.5 with SMTP id a5mr4903634tic.47.1235348386105; Sun, 22 Feb 2009 16:19:46 -0800 (PST) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id 2sm6127330tif.26.2009.02.22.16.19.43 (version=SSLv3 cipher=RC4-MD5); Sun, 22 Feb 2009 16:19:44 -0800 (PST) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Mon, 23 Feb 2009 09:24:41 +0900 From: Pyun YongHyeon Date: Mon, 23 Feb 2009 09:24:40 +0900 To: Fernando Apestegu?a Message-ID: <20090223002440.GA48134@michelle.cdnetworks.co.kr> References: <1bd550a00902200825w3f225d0at99cfd1c6bb63ea0@mail.gmail.com> <20090221015518.GA44336@michelle.cdnetworks.co.kr> <1bd550a00902220915p276b8b61m4b757373a443348a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1bd550a00902220915p276b8b61m4b757373a443348a@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Hackers Subject: Re: FBSD 7.0-p3 NIC driver problem (Realtek) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 00:19:48 -0000 On Sun, Feb 22, 2009 at 06:15:55PM +0100, Fernando Apestegu?a wrote: > On Sat, Feb 21, 2009 at 2:55 AM, Pyun YongHyeon wrote: > > On Fri, Feb 20, 2009 at 05:25:26PM +0100, Fernando Apestegu?a wrote: > >> Hi all, > >> > >> I copy here the mail I sent to freebsd-questions cause I didn't get any answers: > >> > >> > >> Yesterday I updated to 7.1-p3 on AMD64 arch. > >> > >> Since then, the NIC is not detected anymore. ifconfig doesn't show it > >> and I can't connect to the Internet. > >> > >> There were well-known issues with this NIC model before, > >> (http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-11/msg00299.html) > >> but the weird thing is that it seemed to be fine with > >> 7.1-RELEASE and newer till this -p3. > >> > >> It doesn't recognize the card in 4/5 boot sequences (really annoying). > >> > >> Anybody with this problem? > > > > I'm not sure you're suffering from MAC power saving issue of > > RealTek PCIe controller. Sometimes re(4) used to fail to wakeup the > > controller which in turn resulted in 'no driver' for the > > controller. If this is the case you can see "MII without any phy!" > > message in dmesg output. > > You are right, I see that message. > > > r188358(cvs if_re.c 1.95.2.40) should fix the issue so please try > > latest 7-stable or copy if_re.c, if_rlreg.h and if_rl.c from HEAD/ > > 7-stable to your 7.1-RELEASE box and rebuild kernel. > > If you still see the same issue please let me know. > > I copied the files and restarted my computer 5 times and the NIC was > present in all of them. Glad to hear that. > I will watch this issue and I will let you know if I notice more problems. > > Thanks so much for your help. > No problem. > > > > Btw, stable@ is more appropriate list for this type of issues. > > Even if I'm not using -STABLE? > Yes, you're not using CURRENT. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 23 07:23:30 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B816D106566C for ; Mon, 23 Feb 2009 07:23:30 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mx1.freebsd.org (Postfix) with ESMTP id 418298FC13 for ; Mon, 23 Feb 2009 07:23:29 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by ey-out-2122.google.com with SMTP id d26so259608eyd.7 for ; Sun, 22 Feb 2009 23:23:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=M8QC/0xuyOm45axlXuGwwyujMFhq7v3/hbG0R4yZ/O8=; b=kNyIVMVJF3h2oIVqfilSrDpQxps9hWhMPWZZQWKbE61QPzuMCUtG7jkc5s6TwaGxv+ ZgEGxc5umzIxEmQrp5wOcqLBDzTufG9ukcjY8DNACKGjckb69hZfPP/u8ogEopZL1M6/ Q9pPHOzGuobuRzoQzQPJEbGMVPfoXBmImnPJA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=sjlyYOX/J2wSjZpCHLAuhTLzttCFL5VCI5h99Bvz86jJwiZ1Yfg9DQ30XmqW9o6rlY 4hIJKdY8smChe0mAtZ7kjyfJfKHVLlbnyolsFEXKxLdfmeo+yzUF0wBmjg76RhQA7zJl YYAMTOSL6zgtaBv20lRK8DRRrGpnbYFFbjg5A= MIME-Version: 1.0 Received: by 10.210.144.3 with SMTP id r3mr3199140ebd.191.1235373809225; Sun, 22 Feb 2009 23:23:29 -0800 (PST) In-Reply-To: <20090223002440.GA48134@michelle.cdnetworks.co.kr> References: <1bd550a00902200825w3f225d0at99cfd1c6bb63ea0@mail.gmail.com> <20090221015518.GA44336@michelle.cdnetworks.co.kr> <1bd550a00902220915p276b8b61m4b757373a443348a@mail.gmail.com> <20090223002440.GA48134@michelle.cdnetworks.co.kr> Date: Mon, 23 Feb 2009 08:23:29 +0100 Message-ID: <1bd550a00902222323o1580a434mc883b94f26aad74f@mail.gmail.com> From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= To: pyunyh@gmail.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers Subject: Re: FBSD 7.0-p3 NIC driver problem (Realtek) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 07:23:34 -0000 On 2/23/09, Pyun YongHyeon wrote: > On Sun, Feb 22, 2009 at 06:15:55PM +0100, Fernando Apestegu?a wrote: > > On Sat, Feb 21, 2009 at 2:55 AM, Pyun YongHyeon wrote: > > > On Fri, Feb 20, 2009 at 05:25:26PM +0100, Fernando Apestegu?a wrote: > > >> Hi all, > > >> > > >> I copy here the mail I sent to freebsd-questions cause I didn't get any answers: > > >> > > >> > > >> Yesterday I updated to 7.1-p3 on AMD64 arch. > > >> > > >> Since then, the NIC is not detected anymore. ifconfig doesn't show it > > >> and I can't connect to the Internet. > > >> > > >> There were well-known issues with this NIC model before, > > >> (http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2008-11/msg00299.html) > > >> but the weird thing is that it seemed to be fine with > > >> 7.1-RELEASE and newer till this -p3. > > >> > > >> It doesn't recognize the card in 4/5 boot sequences (really annoying). > > >> > > >> Anybody with this problem? > > > > > > I'm not sure you're suffering from MAC power saving issue of > > > RealTek PCIe controller. Sometimes re(4) used to fail to wakeup the > > > controller which in turn resulted in 'no driver' for the > > > controller. If this is the case you can see "MII without any phy!" > > > message in dmesg output. > > > > You are right, I see that message. > > > > > r188358(cvs if_re.c 1.95.2.40) should fix the issue so please try > > > latest 7-stable or copy if_re.c, if_rlreg.h and if_rl.c from HEAD/ > > > 7-stable to your 7.1-RELEASE box and rebuild kernel. > > > If you still see the same issue please let me know. > > > > I copied the files and restarted my computer 5 times and the NIC was > > present in all of them. > > Glad to hear that. > > > I will watch this issue and I will let you know if I notice more problems. > > > > Thanks so much for your help. > > > > No problem. > > > > > > > Btw, stable@ is more appropriate list for this type of issues. > > > > Even if I'm not using -STABLE? > > > > Yes, you're not using CURRENT. OK, I'll keep that in mind. > From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 23 08:11:05 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCCF4106566B for ; Mon, 23 Feb 2009 08:11:05 +0000 (UTC) (envelope-from fergus@cobbled.net) Received: from mail1.slb.deg.dub.stisp.net (mail1.slb.deg.dub.stisp.net [84.203.253.98]) by mx1.freebsd.org (Postfix) with SMTP id 2C3398FC13 for ; Mon, 23 Feb 2009 08:11:04 +0000 (UTC) (envelope-from fergus@cobbled.net) Received: (qmail 18101 invoked from network); 23 Feb 2009 08:10:59 -0000 Received: from unknown (HELO holyman.cobbled.net) (84.203.180.117) by mail1.slb.deg.dub.stisp.net with SMTP; 23 Feb 2009 08:11:03 -0000 Received: by holyman.cobbled.net (Postfix, from userid 16385) id 3A4BC1031D; Mon, 23 Feb 2009 08:10:59 +0000 (UTC) Date: Mon, 23 Feb 2009 08:10:59 +0000 From: n0g0013 To: Brooks Davis Message-ID: <20090223081059.GA11713@holyman.cobbled.net> Mail-Followup-To: Brooks Davis , Julian Elischer , hackers@freebsd.org References: <20090213115426.GA15211@holyman.cobbled.net> <49A0F57E.2030506@elischer.org> <20090222110719.GA16634@holyman.cobbled.net> <20090222222831.GA70072@lor.one-eyed-alien.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090222222831.GA70072@lor.one-eyed-alien.net> Cc: hackers@freebsd.org, Julian Elischer Subject: Re: removal of NGROUPS_MAX dependancy from base X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 08:11:06 -0000 On 22.02-16:28, Brooks Davis wrote: > On Sun, Feb 22, 2009 at 11:07:19AM +0000, ttw+bsd@cobbled.net wrote: > > On 21.02-22:49, Julian Elischer wrote: > > [ ... ] > > > >this patch should remove the dependancy on the definition of > > > >NGROUPS_MAX as a static constant and implement it as a writable > > > >sysconf variable of the same. it should also make the necessary > > > >changes to the codebase to support those. > > [ ... ] > > > What do you do about NFS? > > > I seem to remember that NFWS had a maximum number of groups supported.. > > > > NFS will be supported by mapping 16 groups into the auth_unix structure > > dynamically. my intention is to try and make this transparent by > > allocating moving the 'most used' groups into that mapping as user > > processes check them, however, this is very conceptual at the moment > > and needs more thought as well as validation from others with more > > experience. > > I think this behavior will probably need to be configurable by the > administrator because some sites are probably using groups to supply > negative permissions. It's quite reasionable to argue that's a bad > idea, but we need to take some care since people do occationally use > that "feature". agree. i'm hoping to make the rpc group allocations dynamic and thus, mostly transparent, but would suggest the only consistent way administrators to set permissions (when NFS is required) is to restrict NGROUP_MAX to 16 or less. i intend this to be the default, changed by sysctl/sysconf. my current primary concern is with software that defines it static arrays with a length of NGROUPS_MAX and then forgets to sanitize 'ngroups' count against that maximum but no idea how to catch those except too say that is 'broken'. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 23 16:05:14 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B480106564A for ; Mon, 23 Feb 2009 16:05:14 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: from mx04.pub.collaborativefusion.com (mx04.pub.collaborativefusion.com [206.210.72.84]) by mx1.freebsd.org (Postfix) with ESMTP id 08D498FC1C for ; Mon, 23 Feb 2009 16:05:13 +0000 (UTC) (envelope-from lavalamp@spiritual-machines.org) Received: from [192.168.2.161] ([206.210.89.202]) by mx04.pub.collaborativefusion.com (StrongMail Enterprise 4.1.1.4(4.1.1.4-47689)); Mon, 23 Feb 2009 10:50:08 -0500 X-VirtualServerGroup: Default X-MailingID: 00000::00000::00000::00000::::1 X-SMHeaderMap: mid="X-MailingID" X-Destination-ID: freebsd-hackers@freebsd.org X-SMFBL: ZnJlZWJzZC1oYWNrZXJzQGZyZWVic2Qub3Jn From: "Brian A. Seklecki" To: freebsd-hackers@freebsd.org Content-Type: text/plain Date: Mon, 23 Feb 2009 10:50:07 -0500 Message-Id: <1235404207.31655.2085.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 (2.24.3-1.fc10) Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 23 Feb 2009 16:16:15 +0000 Cc: Kirk Strauser , wmoran@potentialtech.com Subject: Re: shmmax tops out at 2G? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 16:05:14 -0000 > On Wed, 2006-Dec-13 10:50:21 -0500, Bill Moran wrote: > >In response to Bill Moran : > >> sysctl kern.ipc.shmmax=2200000000 > >> kern.ipc.shmmax: 2100000000 -> -2094967296 Someone was nice enough to file a PR related to this: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/130274 We'd be happy to sponsor development in -current to address this limitation. ~BAS From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 23 19:08:31 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3B3A1065930 for ; Mon, 23 Feb 2009 19:08:31 +0000 (UTC) (envelope-from csjp@freebsd.org) Received: from mx-02mtaout02.mts.net (mx-02mtaout02.mts.net [142.161.131.4]) by mx1.freebsd.org (Postfix) with ESMTP id 5FC428FC18 for ; Mon, 23 Feb 2009 19:08:31 +0000 (UTC) (envelope-from csjp@freebsd.org) Received: from wnpgmb021pw-sp03.mts.net ([10.204.128.23]) by mx-02mtaout02.mts.net with ESMTP id <20090223190830.QOGY3962.mx-02mtaout02.mts.net@wnpgmb021pw-sp03.mts.net> for ; Mon, 23 Feb 2009 13:08:30 -0600 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEAFeDokmOoSMW/2dsb2JhbACBbtQPhA8G X-IronPort-AV: E=Sophos;i="4.38,255,1233554400"; d="scan'208";a="63984503" Received: from wnpgmb1307w-ad02-35-22.dynamic.mts.net (HELO jnz.my.domain) ([142.161.35.22]) by wnpgmb021pw-sp03.mts.net with ESMTP; 23 Feb 2009 13:08:29 -0600 Received: from jnz.my.domain (localhost [127.0.0.1]) by jnz.my.domain (8.14.3/8.14.2) with ESMTP id n1NJ8TYh035007; Mon, 23 Feb 2009 13:08:29 -0600 (CST) (envelope-from csjp@jnz.my.domain) Received: (from csjp@localhost) by jnz.my.domain (8.14.3/8.14.2/Submit) id n1NJ8SOP035006; Mon, 23 Feb 2009 13:08:28 -0600 (CST) (envelope-from csjp) Date: Mon, 23 Feb 2009 13:08:28 -0600 From: Christian Peron To: "Brian A. Seklecki" Message-ID: <20090223190828.GA34866@jnz.sqrt.ca> References: <1235404207.31655.2085.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1235404207.31655.2085.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> User-Agent: Mutt/1.4.2.3i Cc: Kirk Strauser , freebsd-hackers@freebsd.org, wmoran@potentialtech.com Subject: Re: shmmax tops out at 2G? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 19:08:33 -0000 This issue has come up a number of times. I was looking into fixing this but I just have not had the time. The basic issue is our shmid_ds structure: struct shmid_ds { struct ipc_perm shm_perm; /* operation permission structure */ int shm_segsz; /* size of segment in bytes */ pid_t shm_lpid; /* process ID of last shared memory op */ pid_t shm_cpid; /* process ID of creator */ short shm_nattch; /* number of current attaches */ time_t shm_atime; /* time of last shmat() */ time_t shm_dtime; /* time of last shmdt() */ time_t shm_ctime; /* time of last change by shmctl() */ void *shm_internal; /* sysv stupidity */ }; Basically the shm_segsz member needs to be switched from 32 bits (int) to 64 bits. The problem is that this breaks the ABI and older versions of postgresql will not work. The solution is to add additional syscalls. However, everytime this issue comes up, the question on whether we should fix struct ipc_perm at the same time is asked. The answer imho is that we should, however this is more complex since semaphores, messaages and shared memory segments all use it. The fixes are straight forward, however making sure we maintain reverse compatability is where things become complicated, especially since there are multiple layers of reverse compat we need to look after. On Mon, Feb 23, 2009 at 10:50:07AM -0500, Brian A. Seklecki wrote: > > On Wed, 2006-Dec-13 10:50:21 -0500, Bill Moran wrote: > > >In response to Bill Moran : > > >> sysctl kern.ipc.shmmax=2200000000 > > >> kern.ipc.shmmax: 2100000000 -> -2094967296 > > Someone was nice enough to file a PR related to this: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/130274 > > We'd be happy to sponsor development in -current to address this > limitation. ~BAS > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 23 19:52:45 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5346C106568D; Mon, 23 Feb 2009 19:52:45 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.freebsd.org (Postfix) with ESMTP id 26B488FC08; Mon, 23 Feb 2009 19:52:45 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.139]) by mxout3.cac.washington.edu (8.14.3+UW08.09/8.14.3+UW09.01) with ESMTP id n1NJqi9l017393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 23 Feb 2009 11:52:44 -0800 X-Auth-Received: from [192.168.10.7] (adsl-99-170-148-198.dsl.pltn13.sbcglobal.net [99.170.148.198]) (authenticated authid=youshi10) by smtp.washington.edu (8.14.3+UW08.09/8.14.3+UW09.01) with ESMTP id n1NJqhK9012855 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 23 Feb 2009 11:52:43 -0800 Message-Id: <78AACD88-3F94-4B39-9122-9C4199DFFDBA@gmail.com> From: Garrett Cooper To: Christian Peron In-Reply-To: <20090223190828.GA34866@jnz.sqrt.ca> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Mon, 23 Feb 2009 11:58:09 -0800 References: <1235404207.31655.2085.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <20090223190828.GA34866@jnz.sqrt.ca> X-Mailer: Apple Mail (2.930.3) X-PMX-Version: 5.5.0.356843, Antispam-Engine: 2.6.1.350677, Antispam-Data: 2009.2.23.194324 X-Uwash-Spam: Gauge=XII, Probability=12%, Report='URI_HOSTNAME_CONTAINS_EQUALS 1, FORGED_FROM_GMAIL 0.1, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, __BOUNCE_CHALLENGE_SUBJ 0, __C230066_P5 0, __CP_URI_IN_BODY 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __FRAUD_419_WEBMAIL 0, __FRAUD_419_WEBMAIL_FROM 0, __FROM_GMAIL 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: Kirk Strauser , freebsd-hackers@freebsd.org, "Brian A. Seklecki" , wmoran@potentialtech.com Subject: Re: shmmax tops out at 2G? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 19:52:45 -0000 On Feb 23, 2009, at 11:08 AM, Christian Peron wrote: > This issue has come up a number of times. I was looking into fixing > this but I > just have not had the time. The basic issue is our shmid_ds > structure: > > struct shmid_ds { > struct ipc_perm shm_perm; /* operation permission > structure */ > int shm_segsz; /* size of segment in bytes */ > pid_t shm_lpid; /* process ID of last shared > memory op */ > pid_t shm_cpid; /* process ID of creator */ > short shm_nattch; /* number of current attaches */ > time_t shm_atime; /* time of last shmat() */ > time_t shm_dtime; /* time of last shmdt() */ > time_t shm_ctime; /* time of last change by > shmctl() */ > void *shm_internal; /* sysv stupidity */ > }; > > > Basically the shm_segsz member needs to be switched from 32 bits > (int) to > 64 bits. The problem is that this breaks the ABI and older versions > of > postgresql will not work. The solution is to add additional syscalls. > > However, everytime this issue comes up, the question on whether we > should > fix struct ipc_perm at the same time is asked. The answer imho is > that > we should, however this is more complex since semaphores, messaages > and > shared memory segments all use it. > > The fixes are straight forward, however making sure we maintain > reverse > compatability is where things become complicated, especially since > there > are multiple layers of reverse compat we need to look after. > > > On Mon, Feb 23, 2009 at 10:50:07AM -0500, Brian A. Seklecki wrote: >>> On Wed, 2006-Dec-13 10:50:21 -0500, Bill Moran wrote: >>>> In response to Bill Moran : >>>>> sysctl kern.ipc.shmmax=2200000000 >>>>> kern.ipc.shmmax: 2100000000 -> -2094967296 >> >> Someone was nice enough to file a PR related to this: >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/130274 >> >> We'd be happy to sponsor development in -current to address this >> limitation. ~BAS Why isn't the field an unsigned int / size_t? I don't see much value in having the size be signed... -Garrett From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 23 20:12:19 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4E191065672; Mon, 23 Feb 2009 20:12:19 +0000 (UTC) (envelope-from csjp@freebsd.org) Received: from mx-01mtaout01.mts.net (mx-01mtaout01.mts.net [142.161.3.3]) by mx1.freebsd.org (Postfix) with ESMTP id 3F0688FC0A; Mon, 23 Feb 2009 20:12:18 +0000 (UTC) (envelope-from csjp@freebsd.org) Received: from wnpgmb013qw-sp03.mts.net ([10.205.128.23]) by mx-01mtaout01.mts.net with ESMTP id <20090223201218.XUOF5684.mx-01mtaout01.mts.net@wnpgmb013qw-sp03.mts.net>; Mon, 23 Feb 2009 14:12:18 -0600 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEAKKRokmOoSMW/2dsb2JhbACBbtQZhA8G X-IronPort-AV: E=Sophos;i="4.38,255,1233554400"; d="scan'208";a="63414369" Received: from wnpgmb1307w-ad02-35-22.dynamic.mts.net (HELO jnz.my.domain) ([142.161.35.22]) by wnpgmb013qw-sp03.mts.net with ESMTP; 23 Feb 2009 14:12:18 -0600 Received: from jnz.my.domain (localhost [127.0.0.1]) by jnz.my.domain (8.14.3/8.14.2) with ESMTP id n1NKCIGC035400; Mon, 23 Feb 2009 14:12:18 -0600 (CST) (envelope-from csjp@jnz.my.domain) Received: (from csjp@localhost) by jnz.my.domain (8.14.3/8.14.2/Submit) id n1NKCHev035399; Mon, 23 Feb 2009 14:12:17 -0600 (CST) (envelope-from csjp) Date: Mon, 23 Feb 2009 14:12:17 -0600 From: Christian Peron To: Garrett Cooper Message-ID: <20090223201217.GA35374@jnz.sqrt.ca> References: <1235404207.31655.2085.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <20090223190828.GA34866@jnz.sqrt.ca> <78AACD88-3F94-4B39-9122-9C4199DFFDBA@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <78AACD88-3F94-4B39-9122-9C4199DFFDBA@gmail.com> User-Agent: Mutt/1.4.2.3i Cc: Kirk Strauser , freebsd-hackers@freebsd.org, Christian Peron , wmoran@potentialtech.com, "Brian A. Seklecki" Subject: Re: shmmax tops out at 2G? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 20:12:19 -0000 On Mon, Feb 23, 2009 at 11:58:09AM -0800, Garrett Cooper wrote: [..] > > Why isn't the field an unsigned int / size_t? I don't see much value > in having the size be signed... No idea :) This code long predates me. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 23 20:32:26 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F5E9106564A; Mon, 23 Feb 2009 20:32:26 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from mail.potentialtech.com (internet.potentialtech.com [66.167.251.6]) by mx1.freebsd.org (Postfix) with ESMTP id 001808FC17; Mon, 23 Feb 2009 20:32:25 +0000 (UTC) (envelope-from wmoran@potentialtech.com) Received: from vanquish.ws.pitbpa0.priv.collaborativefusion.com (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.potentialtech.com (Postfix) with ESMTPSA id 9A6ABEBC0A; Mon, 23 Feb 2009 15:16:12 -0500 (EST) Date: Mon, 23 Feb 2009 15:16:11 -0500 From: Bill Moran To: Christian Peron Message-Id: <20090223151611.af79586c.wmoran@potentialtech.com> In-Reply-To: <20090223201217.GA35374@jnz.sqrt.ca> References: <1235404207.31655.2085.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <20090223190828.GA34866@jnz.sqrt.ca> <78AACD88-3F94-4B39-9122-9C4199DFFDBA@gmail.com> <20090223201217.GA35374@jnz.sqrt.ca> X-Mailer: Sylpheed 2.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 23 Feb 2009 20:42:20 +0000 Cc: Kirk Strauser , Garrett Cooper , "Brian A. Seklecki" , freebsd-hackers@freebsd.org Subject: Re: shmmax tops out at 2G? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2009 20:32:26 -0000 In response to Christian Peron : > On Mon, Feb 23, 2009 at 11:58:09AM -0800, Garrett Cooper wrote: > [..] > > > > Why isn't the field an unsigned int / size_t? I don't see much value > > in having the size be signed... > > No idea :) This code long predates me. It's that way because the original Sun spec for the API said so. It makes little sense to change it just to unsigned. The additional 2G it would give doesn't really solve the tuning problem on a 64G system. This is simply a spec that has become outdated by modern hardware. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 08:09:43 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89D181065670 for ; Tue, 24 Feb 2009 08:09:43 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id 2C0EB8FC12 for ; Tue, 24 Feb 2009 08:09:43 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by yw-out-2324.google.com with SMTP id 2so875139ywt.13 for ; Tue, 24 Feb 2009 00:09:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=SxdbHxYtQL5NKr1lq8YD1lyPLIiu83voEyo90jR6ZzE=; b=F/4NNESeZIB4+cKhnqZ4AgaSASOrDKjWSLLYI/yK3JcvEew6XOYxVlIo4yYd/ivh0C 4+g8vfDwzLmjBIBpeDhWrwA3rkGXzRW8MzsvDiImnZE529Y7inGY67leeumV7CC2RLPP ffoB/UcTBFKQ2OYfN/KCcVSqiL87VR1eICHEM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=rh1swF48uQdcd2qxT4jryzIXqgPQN3Xq9yz6/3VpntBtrYgATq3Y2PDTRupkmhcYSS TeWtiDwlWL5r2WkZTxz+BrXzqucEiPPJquUHPz5KrTNoe5P5RoKqbdRCxVbuZasM0XVE lb4135fdgJtHmt2N0bW3cus+twcbDBU0mgGkY= MIME-Version: 1.0 Received: by 10.90.69.15 with SMTP id r15mr2025042aga.94.1235462982502; Tue, 24 Feb 2009 00:09:42 -0800 (PST) In-Reply-To: <20090223151611.af79586c.wmoran@potentialtech.com> References: <1235404207.31655.2085.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <20090223190828.GA34866@jnz.sqrt.ca> <78AACD88-3F94-4B39-9122-9C4199DFFDBA@gmail.com> <20090223201217.GA35374@jnz.sqrt.ca> <20090223151611.af79586c.wmoran@potentialtech.com> Date: Tue, 24 Feb 2009 00:09:42 -0800 Message-ID: <7d6fde3d0902240009q77e3be85n54c17f7404bc446b@mail.gmail.com> From: Garrett Cooper To: Bill Moran Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Kirk Strauser , freebsd-hackers@freebsd.org, Christian Peron , "Brian A. Seklecki" Subject: Re: shmmax tops out at 2G? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 08:09:43 -0000 On Mon, Feb 23, 2009 at 12:16 PM, Bill Moran wro= te: > In response to Christian Peron : > >> On Mon, Feb 23, 2009 at 11:58:09AM -0800, Garrett Cooper wrote: >> [..] >> > >> > =A0 =A0 Why isn't the field an unsigned int / size_t? I don't see much= value >> > in having the size be signed... >> >> No idea :) This code long predates me. > > It's that way because the original Sun spec for the API said so. > > It makes little sense to change it just to unsigned. =A0The additional 2G > it would give doesn't really solve the tuning problem on a 64G system. > This is simply a spec that has become outdated by modern hardware. Ah, but an unsigned integer on a 64-bit system supports that kind of precision ;). Or are you saying you're crazy enough to run PAE mode with that much RAM 0-o? Then again the bug filer's statement doesn't make sense given the data -- there must be a int32_t used somewhere that's mucking up the system. Trying to compile the test app with -Wall, this is what I see: [gcooper@optimus ~]$ gcc -Wall -o test4 test4.c test4.c: In function 'main': test4.c:11: warning: 'return' with no value, in function returning non-void test4.c:13: warning: format '%zd' expects type 'signed size_t', but argument 2 has type 'int' #include #include int main() { size_t size =3D 2*1024*1024*1024l - 4096; int segid; printf("Requested: %zd\n", size); segid =3D shmget(234, size, IPC_CREAT); if(segid =3D=3D -1) { perror("Died"); return; } printf("SHM ID : %zd\n", segid); } So I'm not 100% sure that this issue isn't a coding error, or the sample app is just incorrect... When the error comes back though from the perror, it returns EINVALID, not ENOMEM or something similar to that. Not sure if it's because the value is truly invalid, or if it's just a bad return code. My 2 cents... -Garrett From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 08:26:50 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D04CE106566B for ; Tue, 24 Feb 2009 08:26:50 +0000 (UTC) (envelope-from neldredge@math.ucsd.edu) Received: from euclid.ucsd.edu (euclid.ucsd.edu [132.239.145.52]) by mx1.freebsd.org (Postfix) with ESMTP id A536A8FC0A for ; Tue, 24 Feb 2009 08:26:50 +0000 (UTC) (envelope-from neldredge@math.ucsd.edu) Received: from zeno.ucsd.edu (zeno.ucsd.edu [132.239.145.22]) by euclid.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id n1O8Qmo07705; Tue, 24 Feb 2009 00:26:48 -0800 (PST) Received: from localhost (neldredg@localhost) by zeno.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id n1O8QmM24399; Tue, 24 Feb 2009 00:26:48 -0800 (PST) X-Authentication-Warning: zeno.ucsd.edu: neldredg owned process doing -bs Date: Tue, 24 Feb 2009 00:26:48 -0800 (PST) From: Nate Eldredge X-X-Sender: neldredg@zeno.ucsd.edu To: Garrett Cooper In-Reply-To: <7d6fde3d0902240009q77e3be85n54c17f7404bc446b@mail.gmail.com> Message-ID: References: <1235404207.31655.2085.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <20090223190828.GA34866@jnz.sqrt.ca> <78AACD88-3F94-4B39-9122-9C4199DFFDBA@gmail.com> <20090223201217.GA35374@jnz.sqrt.ca> <20090223151611.af79586c.wmoran@potentialtech.com> <7d6fde3d0902240009q77e3be85n54c17f7404bc446b@mail.gmail.com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-326116574-1235464008=:29511" Cc: Kirk Strauser , freebsd-hackers@freebsd.org, "Brian A. Seklecki" , Bill Moran , Christian Peron Subject: Re: shmmax tops out at 2G? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 08:26:51 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-326116574-1235464008=:29511 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 24 Feb 2009, Garrett Cooper wrote: > On Mon, Feb 23, 2009 at 12:16 PM, Bill Moran w= rote: >> In response to Christian Peron : >> >>> On Mon, Feb 23, 2009 at 11:58:09AM -0800, Garrett Cooper wrote: >>> [..] >>>> >>>> =A0 =A0 Why isn't the field an unsigned int / size_t? I don't see much= value >>>> in having the size be signed... >>> >>> No idea :) This code long predates me. >> >> It's that way because the original Sun spec for the API said so. >> >> It makes little sense to change it just to unsigned. =A0The additional 2= G >> it would give doesn't really solve the tuning problem on a 64G system. >> This is simply a spec that has become outdated by modern hardware. > > Ah, but an unsigned integer on a 64-bit system supports that kind of > precision ;). Or are you saying you're crazy enough to run PAE mode > with that much RAM 0-o? int and unsigned on amd64 are 32-bit types. To get a 64-bit integer, you= =20 need (unsigned) long. --=20 Nate Eldredge neldredge@math.ucsd.edu ---559023410-326116574-1235464008=:29511-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 17:39:43 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B3571065702 for ; Tue, 24 Feb 2009 17:39:43 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.terabit.net.ua (mail.terabit.net.ua [195.137.202.147]) by mx1.freebsd.org (Postfix) with ESMTP id B224F8FC23 for ; Tue, 24 Feb 2009 17:39:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from skuns.zoral.com.ua ([91.193.166.194] helo=mail.zoral.com.ua) by mail.terabit.net.ua with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1Lc0ax-0002yZ-O3; Tue, 24 Feb 2009 18:57:23 +0200 Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id n1OGCpnk048411 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Feb 2009 18:12:52 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3) with ESMTP id n1OGCpTH020399; Tue, 24 Feb 2009 18:12:51 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n1OGCpUj020398; Tue, 24 Feb 2009 18:12:51 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 24 Feb 2009 18:12:50 +0200 From: Kostik Belousov To: Christian Peron Message-ID: <20090224161250.GP41617@deviant.kiev.zoral.com.ua> References: <1235404207.31655.2085.camel@soundwave.ws.pitbpa0.priv.collaborativefusion.com> <20090223190828.GA34866@jnz.sqrt.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GAVKUSgG5XxJefcs" Content-Disposition: inline In-Reply-To: <20090223190828.GA34866@jnz.sqrt.ca> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: ClamAV version 0.94.2, clamav-milter version 0.94.2 on skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua X-Virus-Scanned: mail.terabit.net.ua 1Lc0ax-0002yZ-O3 0897377afcb4d33c7b2dc2e3c75124d9 X-Terabit: YES Cc: Kirk Strauser , freebsd-hackers@freebsd.org, "Brian A. Seklecki" , wmoran@potentialtech.com Subject: Re: shmmax tops out at 2G? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 17:39:43 -0000 --GAVKUSgG5XxJefcs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 23, 2009 at 01:08:28PM -0600, Christian Peron wrote: > This issue has come up a number of times. I was looking into fixing this= but I > just have not had the time. The basic issue is our shmid_ds structure: >=20 > struct shmid_ds { > struct ipc_perm shm_perm; /* operation permission structure */ > int shm_segsz; /* size of segment in bytes */ > pid_t shm_lpid; /* process ID of last shared memory = op */ > pid_t shm_cpid; /* process ID of creator */ > short shm_nattch; /* number of current attaches */ > time_t shm_atime; /* time of last shmat() */ > time_t shm_dtime; /* time of last shmdt() */ > time_t shm_ctime; /* time of last change by shmctl() */ > void *shm_internal; /* sysv stupidity */ > }; >=20 >=20 > Basically the shm_segsz member needs to be switched from 32 bits (int) to > 64 bits. The problem is that this breaks the ABI and older versions of > postgresql will not work. The solution is to add additional syscalls. >=20 > However, everytime this issue comes up, the question on whether we should > fix struct ipc_perm at the same time is asked. The answer imho is that > we should, however this is more complex since semaphores, messaages and > shared memory segments all use it. >=20 > The fixes are straight forward, however making sure we maintain reverse > compatability is where things become complicated, especially since there > are multiple layers of reverse compat we need to look after. Yes, this is the right solution. Meantime, below is what we use ATM to get over this limitation. The struct shmid_ds is only used for IPC_STAT call in the usermode, ignoring ipcs(1). Allowing it to break for >2Gb segments, we get otherwise good workaround. The luck is that shmget takes size_t instead of int as a segment size. It might be further tweaked to only allow for >2Gb allocation after some sysctl is set, by I do not see a point. diff --git a/sys/kern/sysv_shm.c b/sys/kern/sysv_shm.c index 4e9854d..a945523 100644 --- a/sys/kern/sysv_shm.c +++ b/sys/kern/sysv_shm.c @@ -121,7 +121,8 @@ static sy_call_t *shmcalls[] =3D { #define SHMSEG_ALLOCATED 0x0800 #define SHMSEG_WANTED 0x1000 =20 -static int shm_last_free, shm_nused, shm_committed, shmalloced; +static int shm_last_free, shm_nused, shmalloced; +size_t shm_committed; static struct shmid_kernel *shmsegs; =20 struct shmmap_state { @@ -250,7 +251,7 @@ shm_deallocate_segment(shmseg) =20 vm_object_deallocate(shmseg->u.shm_internal); shmseg->u.shm_internal =3D NULL; - size =3D round_page(shmseg->u.shm_segsz); + size =3D round_page(shmseg->shm_bsegsz); shm_committed -=3D btoc(size); shm_nused--; shmseg->u.shm_perm.mode =3D SHMSEG_FREE; @@ -270,7 +271,7 @@ shm_delete_mapping(struct vmspace *vm, struct shmmap_st= ate *shmmap_s) =20 segnum =3D IPCID_TO_IX(shmmap_s->shmid); shmseg =3D &shmsegs[segnum]; - size =3D round_page(shmseg->u.shm_segsz); + size =3D round_page(shmseg->shm_bsegsz); result =3D vm_map_remove(&vm->vm_map, shmmap_s->va, shmmap_s->va + size); if (result !=3D KERN_SUCCESS) return (EINVAL); @@ -390,7 +391,7 @@ kern_shmat(td, shmid, shmaddr, shmflg) error =3D EMFILE; goto done2; } - size =3D round_page(shmseg->u.shm_segsz); + size =3D round_page(shmseg->shm_bsegsz); #ifdef VM_PROT_READ_IS_EXEC prot =3D VM_PROT_READ | VM_PROT_EXECUTE; #else @@ -422,7 +423,8 @@ kern_shmat(td, shmid, shmaddr, shmflg) =20 vm_object_reference(shmseg->u.shm_internal); rv =3D vm_map_find(&p->p_vmspace->vm_map, shmseg->u.shm_internal, - 0, &attach_va, size, (flags & MAP_FIXED)?0:1, prot, prot, 0); + 0, &attach_va, size, (flags & MAP_FIXED) ? VMFS_NO_SPACE : + VMFS_ANY_SPACE, prot, prot, 0); if (rv !=3D KERN_SUCCESS) { vm_object_deallocate(shmseg->u.shm_internal); error =3D ENOMEM; @@ -720,7 +722,7 @@ shmget_existing(td, uap, mode, segnum) if (error !=3D 0) return (error); #endif - if (uap->size && uap->size > shmseg->u.shm_segsz) + if (uap->size && uap->size > shmseg->shm_bsegsz) return (EINVAL); td->td_retval[0] =3D IXSEQ_TO_IPCID(segnum, shmseg->u.shm_perm); return (0); @@ -732,7 +734,8 @@ shmget_allocate_segment(td, uap, mode) struct shmget_args *uap; int mode; { - int i, segnum, shmid, size; + int i, segnum, shmid; + size_t size; struct ucred *cred =3D td->td_ucred; struct shmid_kernel *shmseg; vm_object_t shm_object; @@ -790,6 +793,7 @@ shmget_allocate_segment(td, uap, mode) shmseg->u.shm_perm.mode =3D (shmseg->u.shm_perm.mode & SHMSEG_WANTED) | (mode & ACCESSPERMS) | SHMSEG_ALLOCATED; shmseg->u.shm_segsz =3D uap->size; + shmseg->shm_bsegsz =3D uap->size; shmseg->u.shm_cpid =3D td->td_proc->p_pid; shmseg->u.shm_lpid =3D shmseg->u.shm_nattch =3D 0; shmseg->u.shm_atime =3D shmseg->u.shm_dtime =3D 0; diff --git a/sys/sys/shm.h b/sys/sys/shm.h index 33ed7b0..c4b1369 100644 --- a/sys/sys/shm.h +++ b/sys/sys/shm.h @@ -108,6 +108,7 @@ struct shminfo { struct shmid_kernel { struct shmid_ds u; struct label *label; /* MAC label */ + size_t shm_bsegsz; }; =20 extern struct shminfo shminfo; diff --git a/usr.bin/ipcs/ipcs.c b/usr.bin/ipcs/ipcs.c index 67364d5..1fd943a 100644 --- a/usr.bin/ipcs/ipcs.c +++ b/usr.bin/ipcs/ipcs.c @@ -452,8 +452,8 @@ print_kshmptr(int i, int option, struct shmid_kernel *k= shmptr) kshmptr->u.shm_nattch); =20 if (option & BIGGEST) - printf(" %12d", - kshmptr->u.shm_segsz); + printf(" %12zu", + kshmptr->shm_bsegsz); =20 if (option & PID) printf(" %12d %12d", --GAVKUSgG5XxJefcs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmkHIIACgkQC3+MBN1Mb4jK1QCeKlR1t5gEnqP1QLW4wAR65WFy MIwAn2/HCHSrWIb5QhW04LgTOKWF5Vwe =DLsh -----END PGP SIGNATURE----- --GAVKUSgG5XxJefcs-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 18:07:47 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2E57106566B for ; Tue, 24 Feb 2009 18:07:47 +0000 (UTC) (envelope-from spsneo@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.184]) by mx1.freebsd.org (Postfix) with ESMTP id 64E308FC1A for ; Tue, 24 Feb 2009 18:07:47 +0000 (UTC) (envelope-from spsneo@gmail.com) Received: by ti-out-0910.google.com with SMTP id a1so2258726tib.3 for ; Tue, 24 Feb 2009 10:07:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=jfKu6dB3DwbIy7O/TV3wfXpODO2QgHnEgRk1lsDIaX8=; b=WU8vvm5N//LUi8fCSfFOs70Q0FIeP8+Q45jd0vqgqo4Fja9XOsqH4KyXAYp9iUYWh6 +F1gNwrCS7FQrXK7VFvdkq2WKrdSDE5Pw2aXxLAgpY4061zSu6uzXhZxcQwNdquLCzBO Zks0zh0RtKDSWQcuy8KDHAesF8BYoFg+7EIpA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=nJnod77h72nzz/Fnz/R3AbngRxSPCSITC49+cP3ioGgrFRYt6znDlsDey46EMsB5yY 6Rfxp2uqQnJrVo7WMkpwKBkXLE9HTxFk18K7uhQWPpquzCB+zc90OreR1fXUI8mJ5RyO +BlECxB7hxRqrIKYiHSfwz8Y6jlg+B4qC9yLE= MIME-Version: 1.0 Received: by 10.110.28.15 with SMTP id b15mr8138751tib.23.1235497435699; Tue, 24 Feb 2009 09:43:55 -0800 (PST) Date: Tue, 24 Feb 2009 23:13:55 +0530 Message-ID: From: Siddharth Prakash Singh To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 18:07:48 -0000 Hi all, I am a student from India. I am willing to contribute to FreeBSD as a google soc participant this year. I would like to suggest an idea. Title: Multicore Aware Process Scheduler. I have not gone through the process scheduler code of Free BSD. Hence, I am not yet aware about the current support for Multicore Architectures. Linux Kernel 2.6.* currently supports SMP, SMT, NUMA architectures. Please do comment and suggest on this idea. Awaiting replies ! -- Siddharth Prakash Singh http://www.spsneo.com From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 18:43:47 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52EA7106564A for ; Tue, 24 Feb 2009 18:43:47 +0000 (UTC) (envelope-from kitchetech@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.28]) by mx1.freebsd.org (Postfix) with ESMTP id 0A41D8FC08 for ; Tue, 24 Feb 2009 18:43:46 +0000 (UTC) (envelope-from kitchetech@gmail.com) Received: by yx-out-2324.google.com with SMTP id 31so988138yxl.13 for ; Tue, 24 Feb 2009 10:43:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=0Yo2OeoBMSrDTYEIeRWgK7BAjmEPuj9NHgEiZ75gVnc=; b=OhgR91vvbKqCpYvWmrysbGwbhhdQl7aqUuJyf4d/xWCyInpoVCPe5fGc08w9CG8J2K X/g8u6O9nFCm0d1mWbWc88wiMkb/wsmSkV5i8mNYjvLzur/VWGwBoVA3bGlX6jkSPtwS TVn4Hmnu/KVylIMKajdyULN/zWdUPTVo2dP5A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=p33e3JlDjPruteekmyLuv289H7fRlbP2yj/EOF3++yFBkb9yxkg0bwEgmV3ozNYFgQ D72CPIQZe6/NKyD/GwNxfBw88ZjQ5+JvkDMnvJq/kDFxZCO1KHrzGtl5s6fipVcOt9bB 9lgvVDGw4wfFISF0T0dYYq4VMDvq6lp9aLcN8= MIME-Version: 1.0 Received: by 10.220.86.203 with SMTP id t11mr1043269vcl.108.1235499027800; Tue, 24 Feb 2009 10:10:27 -0800 (PST) In-Reply-To: References: Date: Tue, 24 Feb 2009 13:10:27 -0500 Message-ID: <28283d910902241010u165c2ba3v51436c440094290e@mail.gmail.com> From: matt donovan To: Siddharth Prakash Singh Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 18:43:47 -0000 On Tue, Feb 24, 2009 at 12:43 PM, Siddharth Prakash Singh wrote: > Hi all, > > I am a student from India. I am willing to contribute to FreeBSD > as a google soc participant this year. I would like to suggest an > idea. > Title: Multicore Aware Process Scheduler. > I have not gone through the process scheduler code of Free BSD. > Hence, I am not yet aware about the current support for Multicore > Architectures. > > Linux Kernel 2.6.* currently supports SMP, SMT, NUMA architectures. > Please do comment and suggest on this idea. > > Awaiting replies ! > > -- > Siddharth Prakash Singh > http://www.spsneo.com > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" you mean ULE which FreeBSD has already but believe it's already an idea for SoC to add things to it From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 19:07:42 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C20F210656ED for ; Tue, 24 Feb 2009 19:07:42 +0000 (UTC) (envelope-from spsneo@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.179]) by mx1.freebsd.org (Postfix) with ESMTP id 615488FC16 for ; Tue, 24 Feb 2009 19:07:42 +0000 (UTC) (envelope-from spsneo@gmail.com) Received: by el-out-1112.google.com with SMTP id r27so1892820ele.13 for ; Tue, 24 Feb 2009 11:07:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OR+LwPWyMK/z/vw6E7Smf1ceJTA0AdSgF/8Z3ke/Y0Y=; b=nsMMn6zDMyA0Zdp2XhgTzJwyi6CpTSjkL0sAUR+exmKXill4+uVbHcw6LEof3+p4p9 CcJI4EMkCRAdChoeaoQvoErNeoYJj8WylxZWkdevWtHPcI8x64gBFrZh4SK70vzwUkZx Eglao6b7K5gzf7Q5GKoVPUQE4x+E2oDb8nVuQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=JuOA1r5UHlsW/bXxKG4CIPl9y98cu8b7YkMxbtG0/KQWIfzIiBIKSyMT+L/XHIeaQ/ 0EU5/XP5chZCyuRR9O9S26pQgU5d03IMAmsn5NivEXNkybbVHgvk4LKUcZOlacwytGWW cx71yjZGgzLpazWN2SBeJJK5WP9NlXLhquwDA= MIME-Version: 1.0 Received: by 10.110.31.5 with SMTP id e5mr8252151tie.35.1235502460454; Tue, 24 Feb 2009 11:07:40 -0800 (PST) In-Reply-To: <1aa142960902241100u671d5f90u769ad98e08fabb43@mail.gmail.com> References: <1aa142960902241100u671d5f90u769ad98e08fabb43@mail.gmail.com> Date: Wed, 25 Feb 2009 00:37:40 +0530 Message-ID: From: Siddharth Prakash Singh To: Ray Mihm Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, jeff@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 19:07:43 -0000 On Wed, Feb 25, 2009 at 12:30 AM, Ray Mihm wrote: >> Title: Multicore Aware Process Scheduler. >> I have not gone through the process scheduler code of Free BSD. >> Hence, I am not yet aware about the current support for Multicore >> Architectures. > > Talk to jeff@freebsd.org, the author of ULE. What are your opinions on this project? What is the scope of this project? > >> Linux Kernel 2.6.* currently supports SMP, SMT, NUMA architectures. Does the current scheduler has support for "CPU affinity/binding", mechanism for distinguishing varying capability of CPUs. > > These may be there already in ULE, although I'm not sure about NUMA. > > Ray > Waiting for your response, Siddharth -- Siddharth Prakash Singh http://www.spsneo.com From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 19:15:42 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BDE9B1065670 for ; Tue, 24 Feb 2009 19:15:42 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (lor.one-eyed-alien.net [69.66.77.232]) by mx1.freebsd.org (Postfix) with ESMTP id 5304C8FC1B for ; Tue, 24 Feb 2009 19:15:42 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.14.3/8.14.3) with ESMTP id n1OJEQIr003085; Tue, 24 Feb 2009 13:14:26 -0600 (CST) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.14.3/8.14.3/Submit) id n1OJEQBt003084; Tue, 24 Feb 2009 13:14:26 -0600 (CST) (envelope-from brooks) Date: Tue, 24 Feb 2009 13:14:26 -0600 From: Brooks Davis To: Siddharth Prakash Singh Message-ID: <20090224191426.GA2947@lor.one-eyed-alien.net> References: <1aa142960902241100u671d5f90u769ad98e08fabb43@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Tue, 24 Feb 2009 13:14:26 -0600 (CST) Cc: freebsd-hackers@freebsd.org, jeff@freebsd.org, Ray Mihm Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 19:15:43 -0000 --pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 25, 2009 at 12:37:40AM +0530, Siddharth Prakash Singh wrote: > On Wed, Feb 25, 2009 at 12:30 AM, Ray Mihm wrote: > >> Title: Multicore Aware Process Scheduler. > >> I have not gone through the process scheduler code of Free BSD. > >> Hence, I am not yet aware about the current support for Multicore > >> Architectures. > > > > Talk to jeff@freebsd.org, the author of ULE. >=20 > What are your opinions on this project? What is the scope of this project? > > > >> Linux Kernel 2.6.* currently supports SMP, SMT, NUMA architectures. >=20 > Does the current scheduler has support for "CPU affinity/binding", > mechanism for distinguishing varying capability of CPUs. I highly recommend you read Jeff's paper on an early version of ULE and look at the code. See also, cpuset(1). Successful summer of code applicants will have demonstrated the ability to follow leads on their own. -- Brooks > > > > These may be there already in ULE, although I'm not sure about NUMA. > > > > Ray > > >=20 > Waiting for your response, >=20 > Siddharth >=20 > --=20 > Siddharth Prakash Singh > http://www.spsneo.com > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >=20 --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iD8DBQFJpEcSXY6L6fI4GtQRAu2OAKDdiQc90O0mY68/hwSvnNXgXhdKrQCfcU9e IiSu5gGIm+kD8PShAmUotFc= =xaj1 -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt-- From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 19:17:25 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA6341065680 for ; Tue, 24 Feb 2009 19:17:25 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id B09D28FC18 for ; Tue, 24 Feb 2009 19:17:25 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n1OJHPoE026668 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 24 Feb 2009 11:17:25 -0800 (PST) (envelope-from sam@freebsd.org) Message-ID: <49A447C5.2020903@freebsd.org> Date: Tue, 24 Feb 2009 11:17:25 -0800 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Siddharth Prakash Singh References: <1aa142960902241100u671d5f90u769ad98e08fabb43@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 19:17:26 -0000 Siddharth Prakash Singh wrote: > On Wed, Feb 25, 2009 at 12:30 AM, Ray Mihm wrote: > >>> Title: Multicore Aware Process Scheduler. >>> I have not gone through the process scheduler code of Free BSD. >>> Hence, I am not yet aware about the current support for Multicore >>> Architectures. >>> >> Talk to jeff@freebsd.org, the author of ULE. >> > > What are your opinions on this project? What is the scope of this project? > >>> Linux Kernel 2.6.* currently supports SMP, SMT, NUMA architectures. >>> > > Does the current scheduler has support for "CPU affinity/binding", > mechanism for distinguishing varying capability of CPUs. > >> These may be there already in ULE, although I'm not sure about NUMA. >> >> Ray >> >> > > Waiting for your response, > > I note you sent this same note to the netbsd mailing lists. You might want to do some more investigation before you propose a project. Sam From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 19:27:44 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1F41106566C for ; Tue, 24 Feb 2009 19:27:44 +0000 (UTC) (envelope-from ray.mihm@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.176]) by mx1.freebsd.org (Postfix) with ESMTP id C6D1C8FC08 for ; Tue, 24 Feb 2009 19:27:44 +0000 (UTC) (envelope-from ray.mihm@gmail.com) Received: by wa-out-1112.google.com with SMTP id k34so1412098wah.27 for ; Tue, 24 Feb 2009 11:27:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=h9SvHBbsHUkvuiyrdp3eEfnWph4cb49++lqtynTOTLA=; b=k7YXiRu4OM9KGq/IAFkInu7IaGwDriqy7WKQrMf+p/w3gEC71nlT3PWSL1h1+V0B+P TXmK813gDz8aqtzsjMuPk65Zumhgj2p3t5QBymxrJR6vxNO1ts66E3HTMB0uxMJCKHru 4+8+X3DssgzMd0gXggZOZmapgMmKEUstK9+F0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=PE+JS9MnceRFt3DpTKONvGbZI0289qtpv+y3kpsmFvh4nZ6hxjOCpK4qCEXbwxH439 zAvG2nGTalVE9vhRzHPGdqnfSV8LuV0AoSyZ1HaRVfaA2XDOAShaBoDnFRH86o0p1wW8 MoDvBG7cBBiYel3MALeBW3GAb0W0rOov/sVlY= MIME-Version: 1.0 Received: by 10.115.47.13 with SMTP id z13mr2383555waj.108.1235502056374; Tue, 24 Feb 2009 11:00:56 -0800 (PST) In-Reply-To: References: Date: Tue, 24 Feb 2009 11:00:56 -0800 Message-ID: <1aa142960902241100u671d5f90u769ad98e08fabb43@mail.gmail.com> From: Ray Mihm To: Siddharth Prakash Singh Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 19:27:45 -0000 > Title: Multicore Aware Process Scheduler. > I have not gone through the process scheduler code of Free BSD. > Hence, I am not yet aware about the current support for Multicore > Architectures. Talk to jeff@freebsd.org, the author of ULE. > Linux Kernel 2.6.* currently supports SMP, SMT, NUMA architectures. These may be there already in ULE, although I'm not sure about NUMA. Ray From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 24 20:55:50 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08D7E106566C for ; Tue, 24 Feb 2009 20:55:50 +0000 (UTC) (envelope-from jgordeev@dir.bg) Received: from dir.bg (mail.dir.bg [194.145.63.28]) by mx1.freebsd.org (Postfix) with ESMTP id 87C9F8FC1B for ; Tue, 24 Feb 2009 20:55:48 +0000 (UTC) (envelope-from jgordeev@dir.bg) Received: from [84.238.192.16] (account jgordeev@dir.bg HELO sometimes2.studgrad.net) by srv.dir.bg (CommuniGate Pro SMTP 5.2.12) with ESMTPSA id 68224002 for freebsd-hackers@FreeBSD.ORG; Tue, 24 Feb 2009 22:25:46 +0200 Message-ID: <49A457CA.20704@dir.bg> Date: Tue, 24 Feb 2009 22:25:46 +0200 From: Jordan Gordeev User-Agent: Mozilla/5.0 (X11; U; DragonFly i386; en-US; rv:1.8.1.19) Gecko/20090204 SeaMonkey/1.1.14 MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG References: <1aa142960902241100u671d5f90u769ad98e08fabb43@mail.gmail.com> <49A447C5.2020903@freebsd.org> In-Reply-To: <49A447C5.2020903@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 20:55:50 -0000 Sam Leffler wrote: > Siddharth Prakash Singh wrote: >> On Wed, Feb 25, 2009 at 12:30 AM, Ray Mihm wrote: >> >>>> Title: Multicore Aware Process Scheduler. >>>> I have not gone through the process scheduler code of Free BSD. >>>> Hence, I am not yet aware about the current support for Multicore >>>> Architectures. >>>> >>> Talk to jeff@freebsd.org, the author of ULE. >>> >> >> What are your opinions on this project? What is the scope of this >> project? >> >>>> Linux Kernel 2.6.* currently supports SMP, SMT, NUMA architectures. >>>> >> >> Does the current scheduler has support for "CPU affinity/binding", >> mechanism for distinguishing varying capability of CPUs. >> >>> These may be there already in ULE, although I'm not sure about NUMA. >>> >>> Ray >>> >>> >> >> Waiting for your response, >> >> > I note you sent this same note to the netbsd mailing lists. You might > want to do some more investigation before you propose a project. > > Sam > It was also sent to the DragonFly mailing lists. :-) From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 25 01:43:07 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74A0D1065670 for ; Wed, 25 Feb 2009 01:43:07 +0000 (UTC) (envelope-from spsneo@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mx1.freebsd.org (Postfix) with ESMTP id 2A7B68FC0A for ; Wed, 25 Feb 2009 01:43:07 +0000 (UTC) (envelope-from spsneo@gmail.com) Received: by yx-out-2324.google.com with SMTP id 31so1078864yxl.13 for ; Tue, 24 Feb 2009 17:43:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WNMSy+Ux+7+d35kv4s3qRoO2GIZreV37pdcf/ApTRsg=; b=AcJOQcLlKu1ZHJb8dZ1mLldsO7bU7BKWneWetaVjTBVPHSsPDCh0bwgy9fp+SnSOWz MUz0uKLK6GHk+RQidW2jTN+F/GsFlJeEHFs0mOvKsq+sGle/rklMn5+RHf6Z+gYfYh6Z AIwKvMiTVI+Z1D8VQIwx27lGmLd1BAZWf6Gvw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=O9KHZkZxLWmXaFTNWnRt0YjUMDF1khTBNG5XL9POR1rfWrL/f0X0tc7QqfueH+F2Bc xAYCotiWBPo4NY4Pt4jkiNF7gesQP0bw9x/kYZ+roIz2IoqV/ttAQTE+QsA2WmhkOVx1 xsR0Y2yTBl1U5erBPwhnC0OzxWxzezhVsJpD0= MIME-Version: 1.0 Received: by 10.110.8.5 with SMTP id 5mr8726427tih.44.1235526185419; Tue, 24 Feb 2009 17:43:05 -0800 (PST) In-Reply-To: <49A457CA.20704@dir.bg> References: <1aa142960902241100u671d5f90u769ad98e08fabb43@mail.gmail.com> <49A447C5.2020903@freebsd.org> <49A457CA.20704@dir.bg> Date: Wed, 25 Feb 2009 07:13:05 +0530 Message-ID: From: Siddharth Prakash Singh To: Jordan Gordeev Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 01:43:07 -0000 Yeah I sent the same proposal to all the *BSD mailing list, because I am interested in doing this project . What's wrong in proposing the same project in all the *BSD organizations? On Wed, Feb 25, 2009 at 1:55 AM, Jordan Gordeev wrote: > Sam Leffler wrote: >> >> Siddharth Prakash Singh wrote: >>> >>> On Wed, Feb 25, 2009 at 12:30 AM, Ray Mihm wrote: >>> >>>>> >>>>> Title: Multicore Aware Process Scheduler. >>>>> I have not gone through the process scheduler code of Free BSD. >>>>> Hence, I am not yet aware about the current support for Multicore >>>>> Architectures. >>>>> >>>> >>>> Talk to jeff@freebsd.org, the author of ULE. >>>> >>> >>> What are your opinions on this project? What is the scope of this >>> project? >>> >>>>> >>>>> Linux Kernel 2.6.* currently supports SMP, SMT, NUMA architectures. >>>>> >>> >>> Does the current scheduler has support for "CPU affinity/binding", >>> mechanism for distinguishing varying capability of CPUs. >>> >>>> >>>> These may be there already in ULE, although I'm not sure about NUMA. >>>> >>>> Ray >>>> >>>> >>> >>> Waiting for your response, >>> >>> >> >> I note you sent this same note to the netbsd mailing lists. =A0You might >> want to do some more investigation before you propose a project. >> >> =A0 Sam >> > It was also sent to the DragonFly mailing lists. :-) > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > --=20 Siddharth Prakash Singh http://www.spsneo.com From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 25 03:34:35 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81CD7106566B for ; Wed, 25 Feb 2009 03:34:35 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail8.sea5.speakeasy.net (mail8.sea5.speakeasy.net [69.17.117.10]) by mx1.freebsd.org (Postfix) with ESMTP id 603138FC0C for ; Wed, 25 Feb 2009 03:34:35 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: (qmail 11687 invoked from network); 25 Feb 2009 03:34:26 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail8.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 25 Feb 2009 03:34:26 -0000 Message-ID: <49A4B9ED.5040705@telenix.org> Date: Tue, 24 Feb 2009 22:24:29 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.19 (X11/20090121) MIME-Version: 1.0 To: FreeBSD-Hackers X-Enigmail-Version: 0.95.5 OpenPGP: id=F3DCA0E9; url=http://pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: x11 status X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 03:34:35 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was wondering, I've lost track of the status of XFree86 on FreeBSD.or really, at all. It looks like all of the Xfree86 servers have been removed from ports. I was looking on the www.Xfree86.org website, and from what I see, it apparently still is generating releases. Also, I downloaded the latest cvs image from Xfree86, and it built FAR easier that xorg, far faster, far simpler to configure ... but when I look into FreeBSD-ports, the few ports which still have the Xfree86 name, they're really cheating (talking about the drivers), they seem to be really xorg drivers, just haven't had their names fixed. No servers for Xfree86 exist in ports anymore, even though it seems trivial to build. Why is that? Is XFree86 not getting any fixes? It seems that their version 4.8.0 is recent, so I'm confused. I just wanted to know if it's missing from ports for some reason, or only because someone wanted it removed? It couldn't be because of a massive prejudice for configure-based ports, is it? (I hope not). -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmkue0ACgkQz62J6PPcoOkgOQCfS+bPR3zcTvckuTtY0fxMBMTT OwsAnjVrFGOLjWhJjDbror4xgzHqjmrV =nFWV -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 25 03:40:49 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 817E51065698 for ; Wed, 25 Feb 2009 03:40:49 +0000 (UTC) (envelope-from kitchetech@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id 3A1648FC13 for ; Wed, 25 Feb 2009 03:40:49 +0000 (UTC) (envelope-from kitchetech@gmail.com) Received: by yx-out-2324.google.com with SMTP id 31so1097945yxl.13 for ; Tue, 24 Feb 2009 19:40:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=9jizdg59lzBp2cgiwvmZ33mImdmqd+70zlUSyu3fvQY=; b=BhHnVqPe1DEcWzVarAqYcrQsX/DZ/pMP+7J8AtADdrnTBN7lJGdRFCfDEKJRo8wlrm dgffaoV0vkgRu/0sip/2I9kI0kiVy0XvzjaJ0LvNM1ipzJkbyxySbMm9gvl9pSjnffyM TIQ2/I4QnIUPCK0rRJAcJEppFzZYgJkVLbd9Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ws/3m4YGyhUTRpieg0b7GxFO83cx8oDe9n+scw0t4SDCqHLirJcUmJpg6sLL5IO7Wo 47u6PnJsW2nwQi2J5CP+prebjXvXtI6gKdTf5jFHYZh9fmt6/TUPFrk1FGkUHKjJX4V7 LCzg9mh7+Kxi0tqVaiTFnchdqqHobKmm1dnUQ= MIME-Version: 1.0 Received: by 10.220.76.144 with SMTP id c16mr1268621vck.17.1235533248603; Tue, 24 Feb 2009 19:40:48 -0800 (PST) In-Reply-To: <49A4B9ED.5040705@telenix.org> References: <49A4B9ED.5040705@telenix.org> Date: Tue, 24 Feb 2009 22:40:48 -0500 Message-ID: <28283d910902241940g6648dbb5yf724508485ce6c3@mail.gmail.com> From: matt donovan To: Chuck Robey Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD-Hackers Subject: Re: x11 status X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 03:40:49 -0000 On Tue, Feb 24, 2009 at 10:24 PM, Chuck Robey wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I was wondering, I've lost track of the status of XFree86 on FreeBSD.or > really, > at all. It looks like all of the Xfree86 servers have been removed from > ports. > I was looking on the www.Xfree86.org website, and from what I see, it > apparently still is generating releases. Also, I downloaded the latest cvs > image from Xfree86, and it built FAR easier that xorg, far faster, far > simpler > to configure ... but when I look into FreeBSD-ports, the few ports which > still > have the Xfree86 name, they're really cheating (talking about the drivers), > they > seem to be really xorg drivers, just haven't had their names fixed. No > servers > for Xfree86 exist in ports anymore, even though it seems trivial to build. > > Why is that? Is XFree86 not getting any fixes? It seems that their > version > 4.8.0 is recent, so I'm confused. I just wanted to know if it's missing > from > ports for some reason, or only because someone wanted it removed? It > couldn't > be because of a massive prejudice for configure-based ports, is it? (I hope > not). > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkmkue0ACgkQz62J6PPcoOkgOQCfS+bPR3zcTvckuTtY0fxMBMTT > OwsAnjVrFGOLjWhJjDbror4xgzHqjmrV > =nFWV > -----END PGP SIGNATURE----- > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" It's due to the fact that not a lot of programs will compile with xfree86. Xorg is the de-facto standard now for graphic server. Pretty much All programs that require a gui at least the ones that depend on X libs use Xorg libs. From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 25 03:57:34 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 90B79106566C for ; Wed, 25 Feb 2009 03:57:34 +0000 (UTC) (envelope-from ray.mihm@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id 45D508FC0A for ; Wed, 25 Feb 2009 03:57:34 +0000 (UTC) (envelope-from ray.mihm@gmail.com) Received: by yw-out-2324.google.com with SMTP id 2so1098874ywt.13 for ; Tue, 24 Feb 2009 19:57:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hag3dpQeTGOJoE44IvYjmsgwlJDv3G19jajEULiCfBA=; b=Tq3BGDqFsb3Rz3laLzJ/EykDqJ9hsaotHJs0Dum+ehKZZxDVI/DNeSUmC1nkpZrpbO okX74OH8Qnt6Dm1ZX282S8sKj3LxGWWcwJJDIwQMUEuZXNl42CfoGG5s3TMZk3xM7AyN SyeJtm6EC4SqfeF80ZZ40IYhKdArmJR3bjqAA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=CZP2IpKeUPyf7dcX58jdqAcAu2voNL+WKrtiLrKmndyBDq2S0RcIbvbqdywN/94QQ6 AKvRTulL98btvhj+1byaNN1n5/9opMBfw+UQUQUe+lk6rCSw05YO4XZ+Aes7hXFMCxPj WCIIElpObc/977kdaG++wqzo2uYXtMYwBSBAg= MIME-Version: 1.0 Received: by 10.100.242.20 with SMTP id p20mr483088anh.83.1235534253755; Tue, 24 Feb 2009 19:57:33 -0800 (PST) In-Reply-To: References: <1aa142960902241100u671d5f90u769ad98e08fabb43@mail.gmail.com> <49A447C5.2020903@freebsd.org> <49A457CA.20704@dir.bg> Date: Tue, 24 Feb 2009 19:57:33 -0800 Message-ID: <1aa142960902241957r28e77868tf2b1ba400f01232@mail.gmail.com> From: Ray Mihm To: Siddharth Prakash Singh Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 03:57:34 -0000 > Yeah I sent the same proposal to all the *BSD mailing list, because I > am interested in doing this project . Have you read what others have said? do. your. homework. first. > What's wrong in proposing the same project in all the *BSD organizations? You wouldn't have asked this question if you'd done your homework. Ray From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 25 06:53:10 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 55867106566B for ; Wed, 25 Feb 2009 06:53:10 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id E6A768FC19 for ; Wed, 25 Feb 2009 06:53:09 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 7A0A71CC64; Wed, 25 Feb 2009 07:53:08 +0100 (CET) Date: Wed, 25 Feb 2009 07:53:08 +0100 From: Ed Schouten To: Chuck Robey Message-ID: <20090225065308.GO19161@hoeg.nl> References: <49A4B9ED.5040705@telenix.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TxukmIqg3MmZ0Kmh" Content-Disposition: inline In-Reply-To: <49A4B9ED.5040705@telenix.org> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: FreeBSD Hackers Subject: Re: x11 status X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 06:53:10 -0000 --TxukmIqg3MmZ0Kmh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Chuck, * Chuck Robey wrote: > I was wondering, I've lost track of the status of XFree86 on > FreeBSD.or really, at all. It looks like all of the Xfree86 servers > have been removed from ports. The XFree86 project has been dying ever since almost all the active development moved to the Xorg-project. Xorg has many new features that XFree86 doesn't have, like hardware compositing and improved device detection. > I was looking on the www.Xfree86.org website, and from what I see, it > apparently still is generating releases. Also, I downloaded the > latest cvs image from Xfree86, and it built FAR easier that xorg, far > faster, far simpler to configure ... Why should it matter how easy it is to build a piece of software? You can just run `make -C /usr/ports/x11/xorg install clean' or `pkg_add -r xorg'. > but when I look into FreeBSD-ports, the few ports which still have the > Xfree86 name, they're really cheating (talking about the drivers), > they seem to be really xorg drivers, just haven't had their names > fixed. This is a naming decision by the Xorg project. For some reason, all drivers are still called xf86-*. It's pretty hard to remove all references to XFree86 in hundreds of megabytes of source code. --=20 Ed Schouten WWW: http://80386.nl/ --TxukmIqg3MmZ0Kmh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmk6tQACgkQ52SDGA2eCwW92gCdEJE3nmRvIhYLRHJ2SPdCbZeN BJcAn0S1h4R1MbexOw+A/3U7SAbS2AED =EwUr -----END PGP SIGNATURE----- --TxukmIqg3MmZ0Kmh-- From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 25 10:38:03 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79621106564A for ; Wed, 25 Feb 2009 10:38:03 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id EBC9B8FC14 for ; Wed, 25 Feb 2009 10:38:02 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (pD9E2DB7D.dip.t-dialin.net [217.226.219.125]) by redbull.bpaserver.net (Postfix) with ESMTP id 96C5A2E147; Wed, 25 Feb 2009 11:37:56 +0100 (CET) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id E65FA13F7B0; Wed, 25 Feb 2009 11:37:51 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1235558271; bh=berJpmfoVfMnNSoRN1K9k6PA9LN1VgtRQ bd1dHI8KEk=; h=Message-ID:Date:From:To:Cc:Subject:References: In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=NwtdLwFTWeXlGiIbSoqIkN3Oaa9/6mP1sBHVQ9IqmlC1+Vn8ydCI0Flb019wRgkR3 Y0L52Hz3M+PA4HPxnhA+sY5/H2RRkOLWnhy1oFv0ld6hW1GWVjdqNl/sMsur0L7OlS+ d6ElQccungYQnD7K6NJE7oR+/XW8lMIMoW7hCLr3cffK9RrYoXFTazPwynhueH6Un66 0cbzV4X37GUd7W092hh8lcYdUDa8UjA/F2B0bhp4UP8Cr0QyMtq6Ol1UG58tVTOa98r Ka4un7YIJ+E3AL69BubuS1MNmS+5mCNZPLbqp2fZB9gphK7MIWVxMVW5o/WpGoUZPko 1mTu+XjdA== Received: (from www@localhost) by webmail.leidinger.net (8.14.3/8.13.8/Submit) id n1PAbpI1054119; Wed, 25 Feb 2009 11:37:51 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Wed, 25 Feb 2009 11:37:51 +0100 Message-ID: <20090225113751.62205vkw7ui1ax6o@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Wed, 25 Feb 2009 11:37:51 +0100 From: Alexander Leidinger To: Siddharth Prakash Singh References: <1aa142960902241100u671d5f90u769ad98e08fabb43@mail.gmail.com> <49A447C5.2020903@freebsd.org> <49A457CA.20704@dir.bg> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.3) / FreeBSD-8.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: 96C5A2E147.E287C X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, ORDB-RBL, SpamAssassin (not cached, score=-14.004, required 6, BAYES_00 -15.00, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, MIME_QP_LONG_LINE 1.40, RDNS_DYNAMIC 0.10, SMILEY -0.50) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Wed, 25 Feb 2009 12:14:27 +0000 Cc: Jordan Gordeev , freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 10:38:04 -0000 Quoting Siddharth Prakash Singh (from Wed, 25 Feb =20 2009 07:13:05 +0530): > Yeah I sent the same proposal to all the *BSD mailing list, because I > am interested in doing this project . What's wrong in proposing the > same project in all the *BSD organizations? As one of the FreeBSD mentors for some GSoC's in the past: nothing is =20 wrong with proposing the same project to several *BSD projects, that's =20 not unusual and happened in the past several times. What's not so nice is to propose something without looking at the =20 existing features in this area. It's not just saying "I want to do =20 something like this". When you submit your proposal to Google, we =20 expect that you looked at the corresponding code and at least know =20 most of the features. You are not supposed to know each line of code =20 or to understand each line of code, but you should know what is there, =20 and what you need to do until your goal is achieved. For example in one of the past GSoC's proposals told that in the XYZ =20 subsystem A, B and C "is missing". They contained a timeframe which =20 explained how much time the student expects until each feature is =20 implemented. For some stuff (API compatibility) even a list of missing =20 functions was presented. You have to understand that in the past we got between 10 and 20 =20 students during the GSoC. For those 10-20 slots there where more than =20 100 proposals (more in the range of 200-300). Those proposals where =20 filtered by Google, so we've seen only those, which where not =20 immediately rejected by Google because of lack of content. Those =20 proposals have to be rated by the FreeBSD committers which are willing =20 to mentor students, and they do this based upon several checkpoints. =20 We look at the proposal and look if it is actually possible to do what =20 is proposed. Not only in general, also during the timeframe of the =20 GSoC and by a student. It is also not important that all features are =20 completed, so if we think that the student is able to e.g. handle 80% =20 of what he proposes and if we also think that this is ok for us, then =20 we give some points to the proposal. This means that the student has =20 to show that he understands what he is talking about and that he has =20 also some insight into what he has to do and some expectation how long =20 it takes. In the end the proposals with the most points (and someone willing to =20 mentor this project) are taken. So the better the proposal is, more =20 likely it will be that the proposal is accepted. When you look at the FreeBSD ideas page, you see the bare minimum what =20 information needs to be in the proposal (nobody needs to write the =20 required skills in a proposal). When we see a proposal which is just a =20 copy of what we have on the ideas page, it will not get that much =20 points, as it doesn't show if the students really understands what he =20 is proposing. Bye, Alexander. > On Wed, Feb 25, 2009 at 1:55 AM, Jordan Gordeev wrote: >> Sam Leffler wrote: >>> >>> Siddharth Prakash Singh wrote: >>>> >>>> On Wed, Feb 25, 2009 at 12:30 AM, Ray Mihm wrote: >>>> >>>>>> >>>>>> Title: Multicore Aware Process Scheduler. >>>>>> I have not gone through the process scheduler code of Free BSD. >>>>>> Hence, I am not yet aware about the current support for Multicore >>>>>> Architectures. >>>>>> >>>>> >>>>> Talk to jeff@freebsd.org, the author of ULE. >>>>> >>>> >>>> What are your opinions on this project? What is the scope of this >>>> project? >>>> >>>>>> >>>>>> Linux Kernel 2.6.* currently supports SMP, SMT, NUMA architectures. >>>>>> >>>> >>>> Does the current scheduler has support for "CPU affinity/binding", >>>> mechanism for distinguishing varying capability of CPUs. >>>> >>>>> >>>>> These may be there already in ULE, although I'm not sure about NUMA. >>>>> >>>>> Ray >>>>> >>>>> >>>> >>>> Waiting for your response, >>>> >>>> >>> >>> I note you sent this same note to the netbsd mailing lists. =C2=A0You mi= ght >>> want to do some more investigation before you propose a project. >>> >>> =C2=A0 Sam >>> >> It was also sent to the DragonFly mailing lists. :-) >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " >> > > > > -- > Siddharth Prakash Singh > http://www.spsneo.com > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > --=20 There is a certain impertinence in allowing oneself to be burned for an opinion. =09=09-- Anatole France http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 25 22:12:21 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B300110657DB for ; Wed, 25 Feb 2009 22:12:21 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 96D9F8FC08 for ; Wed, 25 Feb 2009 22:12:21 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 08FC88C063; Wed, 25 Feb 2009 16:12:21 -0600 (CST) Date: Wed, 25 Feb 2009 16:12:21 -0600 From: Mark Linimon To: Chuck Robey Message-ID: <20090225221221.GA2289@lonesome.com> References: <49A4B9ED.5040705@telenix.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49A4B9ED.5040705@telenix.org> User-Agent: Mutt/1.5.18 (2008-05-17) X-Mailman-Approved-At: Wed, 25 Feb 2009 22:26:08 +0000 Cc: FreeBSD-Hackers Subject: Re: x11 status X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 22:12:22 -0000 On Tue, Feb 24, 2009 at 10:24:29PM -0500, Chuck Robey wrote: > Why is that? Is XFree86 not getting any fixes? We didn't have anyone that wanted to support it after we switched the default to xorg. (We actually need more people willing to support xorg, as well). mcl From owner-freebsd-hackers@FreeBSD.ORG Wed Feb 25 23:38:50 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B59A106566C; Wed, 25 Feb 2009 23:38:50 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id A99328FC1C; Wed, 25 Feb 2009 23:38:49 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 9D88628448; Thu, 26 Feb 2009 07:38:48 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id AFEBCEDC96A; Thu, 26 Feb 2009 07:38:47 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id XjZQQG6tWaNR; Thu, 26 Feb 2009 07:38:42 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-62.dsl.pltn13.sbcglobal.net [76.237.33.62]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 3FDD1EB5D7A; Thu, 26 Feb 2009 07:38:40 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:subject:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=B2L7ixstYmnFgHsdcYytcQepp9w8uG0Ke/uZ25GuCNq5Fa00V7n7FvigwxGpYTJd5 Wyu/C7HNVr4LVLDsluBOA== Message-ID: <49A5D67C.8080102@delphij.net> Date: Wed, 25 Feb 2009 15:38:36 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.19 (X11/20090217) MIME-Version: 1.0 To: freebsd-hackers , kan@FreeBSD.org X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: How to change an interface? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2009 23:38:50 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Just wanted to confirm that the following procedure to change an existing interface: - Remove the symbol in question from all previous FBSD_1.* namespaces with their corresponding Symbol.map files; - Add the new symbol into latest FBSD_1.* namespace, say, FBSD_1.1 for now, into corresponding Symbol.map files; - Create a new file containing the compatibility shims with prefix __ and suffix of something indicating its obsoleteness, e.g. _44bsd. For instance, for function foo(), the shim function would be called __foo_44bsd(); - At the tail of the shim file, add glues for the old symbols like this: __sym_compat(foo, __foo_44bsd, FBSD_1.0); - Double check to make sure that new .so would work with old binaries. Is that correct? Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkml1nwACgkQi+vbBBjt66CgLwCgojrOaeSyuNHdHQyzxA0+UEMq PREAn0rFE8zpFez0WbccVAir8Nhf/AK0 =MBeo -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 00:21:21 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FB491065676; Thu, 26 Feb 2009 00:21:21 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id B85B18FC1C; Thu, 26 Feb 2009 00:21:20 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n1Q02l9R024884; Wed, 25 Feb 2009 19:02:47 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Wed, 25 Feb 2009 19:02:47 -0500 (EST) Date: Wed, 25 Feb 2009 19:02:47 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: d@delphij.net In-Reply-To: <49A5D67C.8080102@delphij.net> Message-ID: References: <49A5D67C.8080102@delphij.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: kan@freebsd.org, freebsd-hackers Subject: Re: How to change an interface? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 00:21:47 -0000 On Wed, 25 Feb 2009, Xin LI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > Just wanted to confirm that the following procedure to change an > existing interface: > > - Remove the symbol in question from all previous FBSD_1.* namespaces > with their corresponding Symbol.map files; > > - Add the new symbol into latest FBSD_1.* namespace, say, FBSD_1.1 for > now, into corresponding Symbol.map files; > > - Create a new file containing the compatibility shims with prefix __ > and suffix of something indicating its obsoleteness, e.g. _44bsd. For > instance, for function foo(), the shim function would be called > __foo_44bsd(); > > - At the tail of the shim file, add glues for the old symbols like this: > > __sym_compat(foo, __foo_44bsd, FBSD_1.0); > > - Double check to make sure that new .so would work with old binaries. > > Is that correct? Yes, I believe that is correct. I also think that the awk script that processes the Symbol.map files will also warn you if the symbol is multiply declared. -- DE From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 01:27:46 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E383F1065672 for ; Thu, 26 Feb 2009 01:27:46 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (h-66-166-149-52.snvacaid.covad.net [66.166.149.52]) by mx1.freebsd.org (Postfix) with ESMTP id 916458FC08 for ; Thu, 26 Feb 2009 01:27:46 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by monday.kientzle.com (8.14.3/8.14.3) id n1PNejnp010682; Wed, 25 Feb 2009 15:40:45 -0800 (PST) (envelope-from kientzle@freebsd.org) Received: from [10.123.2.23] (10.123.1.2 [10.123.1.2]) by monday.kientzle.com with SMTP id axc84rjepyyjjza978cmxd2xwi; Wed, 25 Feb 2009 15:40:45 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <49A5D6FC.1090800@freebsd.org> Date: Wed, 25 Feb 2009 15:40:44 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Siddharth Prakash Singh References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 01:27:47 -0000 Siddharth Prakash Singh wrote: > > I am a student from India. I am willing to contribute to FreeBSD > as a google soc participant this year. I would like to suggest an > idea. > Title: Multicore Aware Process Scheduler. > I have not gone through the process scheduler code of Free BSD. > Hence, I am not yet aware about the current support for Multicore > Architectures. Since you posted to a lot of different lists, I think you probably don't already use FreeBSD. (If you did, why would you post to NetBSD and DragonflyBSD lists?) Scheduler work is quite complex and interacts heavily with the rest of the system; it may not be a good choice for someone who doesn't already have a lot of experience with FreeBSD. You should probably tell us a little more about yourself: What kind of student? Graduate? Undergraduate? Are you in a CS program or some other engineering program? Do you use FreeBSD? How long have you used it? What do you do with it? Have you read Kirk McKusick's book on FreeBSD internals? Have you built and installed a FreeBSD system from source code? Have you taken classes on OS internals? How much C programming have you done? What areas of FreeBSD have you had the most problems with? How would you make those areas better? Tim Kientzle From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 02:24:41 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8524106566C for ; Thu, 26 Feb 2009 02:24:41 +0000 (UTC) (envelope-from fbsd.hackers@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 717918FC14 for ; Thu, 26 Feb 2009 02:24:41 +0000 (UTC) (envelope-from fbsd.hackers@rachie.is-a-geek.net) Received: from localhost (mail.lan.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id C8A95AFC1FF for ; Wed, 25 Feb 2009 17:24:40 -0900 (AKST) From: Mel To: freebsd-hackers@freebsd.org Date: Wed, 25 Feb 2009 17:24:40 -0900 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_o1fpJvCx4PioHXE" Message-Id: <200902251724.40212.fbsd.hackers@rachie.is-a-geek.net> Subject: [PATCH] Support for thresholds in du(1) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 02:24:42 -0000 --Boundary-00=_o1fpJvCx4PioHXE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, attached is a small patch to add threshold support to du(1). I've been using it on 7-STABLE machines for a while, cause I got tired of the noise I get when sorting and then reformatting to human-readable. Especially since sorting isn't part of the equasion "I'd like to see all dirs exceeding a given size". I've not updated the manpage on -STABLE yet, should be the same as HEAD. Example usage: # du -xht 20m . 29M ./contrib/binutils 52M ./contrib/gcc 237M ./contrib 35M ./crypto 28M ./lib 20M ./share 55M ./sys/dev 139M ./sys 545M . I'll file a PR for it, if there's no objections to this feature / implementation, the style(9) or the usage of -t. -- Mel --Boundary-00=_o1fpJvCx4PioHXE Content-Type: text/x-diff; charset="iso 8859-15"; name="du.HEAD.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="du.HEAD.diff" Index: usr.bin/du/du.1 =================================================================== RCS file: /home/ncvs/src/usr.bin/du/du.1,v retrieving revision 1.34 diff -u -r1.34 du.1 --- usr.bin/du/du.1 6 Nov 2008 16:30:38 -0000 1.34 +++ usr.bin/du/du.1 26 Feb 2009 01:58:25 -0000 @@ -42,7 +42,7 @@ .Nm .Op Fl A .Op Fl H | L | P -.Op Fl a | s | d Ar depth +.Op Fl a | s | d Ar depth | t Ar threshold .Op Fl c .Op Fl l .Op Fl h | k | m | B Ar blocksize @@ -106,6 +106,13 @@ .It Fl s Display an entry for each specified file. (Equivalent to +.It Fl t Ar threshold +Display only entries for which the size exceeds +.Ar threshold +, which can be given in bytes (default), kB, MB or GB, by appending k, m, +or g respectively. +.Ar threshold +cannot exceeds the platform's OFF_MAX. .Fl d Li 0 ) .It Fl d Ar depth Display an entry for all files and directories Index: usr.bin/du/du.c =================================================================== RCS file: /home/ncvs/src/usr.bin/du/du.c,v retrieving revision 1.49 diff -u -r1.49 du.c --- usr.bin/du/du.c 6 Nov 2008 23:55:28 -0000 1.49 +++ usr.bin/du/du.c 26 Feb 2009 02:03:48 -0000 @@ -87,7 +87,7 @@ { FTS *fts; FTSENT *p; - off_t savednumber, curblocks; + off_t savednumber, curblocks, threshold; int ftsoptions; int listall; int depth; @@ -95,6 +95,8 @@ int hflag, lflag, ch, notused, rval; char **save; static char dot[] = "."; + char last; + int multi = 1; setlocale(LC_ALL, ""); @@ -103,13 +105,13 @@ save = argv; ftsoptions = 0; - savednumber = 0; + savednumber = threshold = 0; cblocksize = DEV_BSIZE; blocksize = 0; depth = INT_MAX; SLIST_INIT(&ignores); - while ((ch = getopt(argc, argv, "AB:HI:LPasd:chklmnrx")) != -1) + while ((ch = getopt(argc, argv, "AB:HI:LPasd:chklmnrt:x")) != -1) switch (ch) { case 'A': Aflag = 1; @@ -177,6 +179,40 @@ break; case 'r': /* Compatibility. */ break; + case 't' : + last = optarg[strlen(optarg)-1]; + switch(last) + { + case 'k' : + case 'K' : + multi = 1024; + break; + case 'm' : + case 'M' : + multi = 1024*1024; + break; + case 'G' : + case 'g' : + multi = 1024*1024*1024; + break; + default : + break; + } + if( multi > 1 ) + optarg[strlen(optarg)-1] = '\0'; + threshold = (off_t)strtoll(optarg, NULL, 10); + if( errno == ERANGE || threshold < 0 ) + { + warn("Invalid threshold: %s", optarg); + usage(); + } + if( threshold > OFF_MAX / multi ) + { + warnx("Threshold too large"); + usage(); + } + threshold *= multi; + break; case 'x': ftsoptions |= FTS_XDEV; break; @@ -267,7 +303,8 @@ p->fts_parent->fts_bignum += p->fts_bignum += curblocks; - if (p->fts_level <= depth) { + if (p->fts_level <= depth && threshold < howmany(p->fts_bignum * + cblocksize, blocksize)) { if (hflag) { prthumanval(p->fts_bignum); (void)printf("\t%s\n", p->fts_path); --Boundary-00=_o1fpJvCx4PioHXE Content-Type: text/x-diff; charset="iso 8859-15"; name="du.RELENG_7.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="du.RELENG_7.diff" Index: usr.bin/du/du.c =================================================================== RCS file: /home/ncvs/src/usr.bin/du/du.c,v retrieving revision 1.42.2.1 diff -u -r1.42.2.1 du.c --- usr.bin/du/du.c 15 Jan 2009 03:48:49 -0000 1.42.2.1 +++ usr.bin/du/du.c 26 Feb 2009 02:02:49 -0000 @@ -86,6 +86,7 @@ FTS *fts; FTSENT *p; off_t savednumber = 0; + off_t threshold = 0; long blocksize; int ftsoptions; int listall; @@ -94,6 +95,8 @@ int hflag, lflag, ch, notused, rval; char **save; static char dot[] = "."; + char last; + int multi = 1; setlocale(LC_ALL, ""); @@ -105,7 +108,7 @@ depth = INT_MAX; SLIST_INIT(&ignores); - while ((ch = getopt(argc, argv, "HI:LPasd:chklmnrx")) != -1) + while ((ch = getopt(argc, argv, "HI:LPasd:chklmnrt:x")) != -1) switch (ch) { case 'H': Hflag = 1; @@ -161,6 +164,40 @@ break; case 'r': /* Compatibility. */ break; + case 't' : + last = optarg[strlen(optarg)-1]; + switch(last) + { + case 'k' : + case 'K' : + multi = 1024; + break; + case 'm' : + case 'M' : + multi = 1024*1024; + break; + case 'G' : + case 'g' : + multi = 1024*1024*1024; + break; + default : + break; + } + if( multi > 1 ) + optarg[strlen(optarg)-1] = '\0'; + threshold = (off_t)strtoll(optarg, NULL, 10); + if( errno == ERANGE || threshold < 0 ) + { + warn("Invalid threshold: %s", optarg); + usage(); + } + if( threshold > OFF_MAX / multi ) + { + warnx("Threshold too large"); + usage(); + } + threshold *= multi; + break; case 'x': ftsoptions |= FTS_XDEV; break; @@ -239,7 +276,7 @@ p->fts_parent->fts_bignum += p->fts_bignum += p->fts_statp->st_blocks; - if (p->fts_level <= depth) { + if (p->fts_level <= depth && threshold < howmany(p->fts_bignum * DEV_BSIZE, blocksize)) { if (hflag) { (void) prthumanval(howmany(p->fts_bignum, blocksize)); (void) printf("\t%s\n", p->fts_path); --Boundary-00=_o1fpJvCx4PioHXE-- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 03:37:02 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1D37106566C for ; Thu, 26 Feb 2009 03:37:02 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 9738C8FC12 for ; Thu, 26 Feb 2009 03:37:02 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id C7E2228449 for ; Thu, 26 Feb 2009 11:37:00 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 7B8BAEB62D7; Thu, 26 Feb 2009 11:36:59 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id NQYPKrMq+oXJ; Thu, 26 Feb 2009 11:36:51 +0800 (CST) Received: from charlie.delphij.net (c-69-181-141-49.hsd1.ca.comcast.net [69.181.141.49]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 208C3EB5D3B; Thu, 26 Feb 2009 11:36:49 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=P12V+xuBZPNAyIb/8GR5sEq+Bw/oLhHDAtcE31BpDH8mk+GdDHtHClQjUQE8ERlcH HQWOA5QSvz3CGt/NMd10A== Message-ID: <49A60E4D.5040605@delphij.net> Date: Wed, 25 Feb 2009 19:36:45 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.19 (X11/20090217) MIME-Version: 1.0 To: Mel References: <200902251724.40212.fbsd.hackers@rachie.is-a-geek.net> In-Reply-To: <200902251724.40212.fbsd.hackers@rachie.is-a-geek.net> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: [PATCH] Support for thresholds in du(1) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 03:37:03 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mel wrote: [...] > I'll file a PR for it, if there's no objections to this feature / > implementation, the style(9) or the usage of -t. One comment: you may want to consider using expand_number(3) instead of rolling your own version Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmmDk0ACgkQi+vbBBjt66A1pgCghpIS/bOgflo0JKNBlKZlBzDf H0IAn21ZJNk1fT6YWDzO0e6nK4dUmJd0 =FFjB -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 04:03:21 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C093B106566B for ; Thu, 26 Feb 2009 04:03:21 +0000 (UTC) (envelope-from fbsd.hackers@rachie.is-a-geek.net) Received: from mail.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 936FC8FC1A for ; Thu, 26 Feb 2009 04:03:21 +0000 (UTC) (envelope-from fbsd.hackers@rachie.is-a-geek.net) Received: from localhost (mail.lan.rachie.is-a-geek.net [192.168.2.101]) by mail.rachie.is-a-geek.net (Postfix) with ESMTP id 0F557AFC1FF; Wed, 25 Feb 2009 19:03:21 -0900 (AKST) From: Mel To: freebsd-hackers@freebsd.org, d@delphij.net Date: Wed, 25 Feb 2009 19:03:20 -0900 User-Agent: KMail/1.9.10 References: <200902251724.40212.fbsd.hackers@rachie.is-a-geek.net> <49A60E4D.5040605@delphij.net> In-Reply-To: <49A60E4D.5040605@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200902251903.20430.fbsd.hackers@rachie.is-a-geek.net> Cc: Subject: Re: [PATCH] Support for thresholds in du(1) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 04:03:22 -0000 On Wednesday 25 February 2009 18:36:45 Xin LI wrote: > Mel wrote: > [...] > > > I'll file a PR for it, if there's no objections to this feature / > > implementation, the style(9) or the usage of -t. > > One comment: you may want to consider using expand_number(3) instead of > rolling your own version Cool thanks, didn't know about that one and was actually considering a request for this API. Maybe strtonum/atoi/stroll and friends should .Xr this API? -- Mel From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 04:25:04 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9252106564A for ; Thu, 26 Feb 2009 04:25:04 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8CB288FC16 for ; Thu, 26 Feb 2009 04:25:04 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id 4C19D28448 for ; Thu, 26 Feb 2009 12:25:03 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id B32DDEB5D3B; Thu, 26 Feb 2009 12:25:02 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id xP2inCFozZkb; Thu, 26 Feb 2009 12:24:57 +0800 (CST) Received: from charlie.delphij.net (c-69-181-141-49.hsd1.ca.comcast.net [69.181.141.49]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 86FDFEB5CE7; Thu, 26 Feb 2009 12:24:56 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:cc:subject:references:in-reply-to: x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=jICOjvuUBfTtcAlmWApAM3iQmGUbJzQmCzP69bcVMM9DFyPUMF6zt0EFAuCIS/1uu FHnFiDeHSV7HMJ20OKdjw== Message-ID: <49A61995.5040500@delphij.net> Date: Wed, 25 Feb 2009 20:24:53 -0800 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.19 (X11/20090217) MIME-Version: 1.0 To: Mel References: <200902251724.40212.fbsd.hackers@rachie.is-a-geek.net> <49A60E4D.5040605@delphij.net> <200902251903.20430.fbsd.hackers@rachie.is-a-geek.net> In-Reply-To: <200902251903.20430.fbsd.hackers@rachie.is-a-geek.net> X-Enigmail-Version: 0.95.7 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, d@delphij.net Subject: Re: [PATCH] Support for thresholds in du(1) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 04:25:05 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mel wrote: > On Wednesday 25 February 2009 18:36:45 Xin LI wrote: >> Mel wrote: >> [...] >> >>> I'll file a PR for it, if there's no objections to this feature / >>> implementation, the style(9) or the usage of -t. >> One comment: you may want to consider using expand_number(3) instead of >> rolling your own version > > Cool thanks, didn't know about that one and was actually considering a request > for this API. Maybe strtonum/atoi/stroll and friends should .Xr this API? Maybe, perhaps also humanize_numbers... We may also want NetBSD's dehumanize_number as well... - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmmGZUACgkQi+vbBBjt66DX0ACfSge9+MA5P98MOYf4LfF+rKn8 Nq8AoLCko53l4YKQrZUQW1PJp9oUVAw4 =6ok+ -----END PGP SIGNATURE----- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 12:23:52 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7A0EB1065672 for ; Thu, 26 Feb 2009 12:23:52 +0000 (UTC) (envelope-from spsneo@gmail.com) Received: from mail-gx0-f176.google.com (mail-gx0-f176.google.com [209.85.217.176]) by mx1.freebsd.org (Postfix) with ESMTP id 0AD928FC1D for ; Thu, 26 Feb 2009 12:23:51 +0000 (UTC) (envelope-from spsneo@gmail.com) Received: by gxk24 with SMTP id 24so1416985gxk.19 for ; Thu, 26 Feb 2009 04:23:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Ejoi3Q1l+lU82vS7gKhRcJzlxu1mtcCUNv4XB13xs9I=; b=Gsn0dOmgcRyutxk6+xL8OusMegPnFd4Xb6j7GNtiCY8msALtC2toXk1XPucWVeeL5S WOlddjT7PNEC/ewMaddYP9bzbGpW3szNQOfSScotnRmlGJa33fMUWuabVMX4xZ0VSrcw 04Y7tMfC5VM+2L3980KajzLS7ia6Gjf/+Taok= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=di4At7O3ITXuogAmO6dOA22xV2ejo9ADfz230tpV4ckoZgTGuA0B1dUIt7w/YJCetc 6TQM8g5EL/ZFOoGtS/Vl/z1hKZyv1X0+SmommT5E1VYS3vHkLgc9Sn5ZNpzuiyQIqxHs l45cf3AiZBK+itM4jtGHC51/PhhFVlkMuvuOI= MIME-Version: 1.0 Received: by 10.110.16.9 with SMTP id 9mr1830291tip.14.1235651028268; Thu, 26 Feb 2009 04:23:48 -0800 (PST) In-Reply-To: <49A5D6FC.1090800@freebsd.org> References: <49A5D6FC.1090800@freebsd.org> Date: Thu, 26 Feb 2009 17:53:48 +0530 Message-ID: From: Siddharth Prakash Singh To: Tim Kientzle Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 12:23:52 -0000 On Thu, Feb 26, 2009 at 5:10 AM, Tim Kientzle wrote: > Siddharth Prakash Singh wrote: >> >> I am a student from India. I am willing to contribute to FreeBSD >> as a google soc participant this year. I would like to suggest an >> idea. >> Title: Multicore Aware Process Scheduler. >> I have not gone through the process scheduler code of Free BSD. >> Hence, I am not yet aware about the current support for Multicore >> Architectures. > > Since you posted to a lot of different lists, I > think you probably don't already use FreeBSD. > (If you did, why would you post to NetBSD and > DragonflyBSD lists?) =A0Scheduler work is quite complex > and interacts heavily with the rest of the system; > it may not be a good choice for someone who doesn't > already have a lot of experience with FreeBSD. > > You should probably tell us a little more about yourself: > > What kind of student? =A0Graduate? =A0Undergraduate? > Are you in a CS program or some other engineering program? I am junior undergraduate student at CS department of Indian Institute Of Technology, India. > > Do you use FreeBSD? =A0How long have you used it? > What do you do with it? No, I haven't really used FreeBSD much. I have been using Linux since long! > > Have you read Kirk McKusick's book on FreeBSD internals? No. But I have sound knowledge of Linux and Minix Kernel. > > Have you built and installed a FreeBSD system from source code? No, But I have built and installed a Linux system from source code. > > Have you taken classes on OS internals? Yes, I have taken a course on OS internal last semester only. Ans I worked on Pintos Kernel as a part of the course. > > How much C programming have you done? I have a tremendous experience of C coding. > > What areas of FreeBSD have you had the most problems with? > How would you make those areas better? > > Tim Kientzle > I am aware that I am new to FreeBSD, but that doesn't really mean I am not qualified. --=20 Siddharth Prakash Singh http://www.spsneo.com From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 12:41:37 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2F38106566C; Thu, 26 Feb 2009 12:41:37 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3]) by mx1.freebsd.org (Postfix) with ESMTP id 5830B8FC0C; Thu, 26 Feb 2009 12:41:37 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from [195.4.92.16] (helo=6.mx.freenet.de) by mout1.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #76) id 1LcfYW-0008Bs-5u; Thu, 26 Feb 2009 13:41:36 +0100 Received: from teca0.t.pppool.de ([89.55.236.160]:16474 helo=ernst.jennejohn.org) by 6.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #76) id 1LcfYV-0003Fu-TN; Thu, 26 Feb 2009 13:41:36 +0100 Date: Thu, 26 Feb 2009 13:41:35 +0100 From: Gary Jennejohn To: Siddharth Prakash Singh Message-ID: <20090226134135.156d3b86@ernst.jennejohn.org> In-Reply-To: References: <49A5D6FC.1090800@freebsd.org> X-Mailer: Claws Mail 3.7.0 (GTK+ 2.14.7; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Tim Kientzle Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 12:41:38 -0000 On Thu, 26 Feb 2009 17:53:48 +0530 Siddharth Prakash Singh wrote: > > Do you use FreeBSD? __How long have you used it? > > What do you do with it? > No, I haven't really used FreeBSD much. I have been using Linux since long! > > > > Have you read Kirk McKusick's book on FreeBSD internals? > No. But I have sound knowledge of Linux and Minix Kernel. > > Having done development on both FreeBSD and Linux I can authoritatively state that they're totally different animals. But just because you only have Linux knowledge doesn't exclude you from doing FreeBSD development. It will just take a while to get up to speed. --- Gary Jennejohn From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 16:23:20 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFD0A106566B; Thu, 26 Feb 2009 16:23:20 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B8CE78FC0C; Thu, 26 Feb 2009 16:23:20 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 516AA46BA0; Thu, 26 Feb 2009 11:23:20 -0500 (EST) Date: Thu, 26 Feb 2009 16:23:20 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Tim Kientzle In-Reply-To: <49A5D6FC.1090800@freebsd.org> Message-ID: References: <49A5D6FC.1090800@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Siddharth Prakash Singh , freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 16:23:21 -0000 On Wed, 25 Feb 2009, Tim Kientzle wrote: >> I have not gone through the process scheduler code of Free BSD. Hence, I am >> not yet aware about the current support for Multicore Architectures. > > Since you posted to a lot of different lists, I think you probably don't > already use FreeBSD. (If you did, why would you post to NetBSD and > DragonflyBSD lists?) Scheduler work is quite complex and interacts heavily > with the rest of the system; it may not be a good choice for someone who > doesn't already have a lot of experience with FreeBSD. All the things you say are true, but let's not be too hard on the new guy, however -- many of our GSoC students don't have previous FreeBSD kernel-hacking experience. However, it does mean that they have to pick project ideas that are well-suited to a significant warmup and investigation period on the front end of the project. I'm also not convinced that a scheduler project along these lines would be the most successful, but I wonder if a more experimental-spin proposal for looking at how to investigate poor scheduling decisions using dtrace, instrumentation and metrics to help us understand performance on NUMA systems, and exploring the impact of heuristics might go a long way. As our ULE scheduler has most of the non-NUMA features suggested in the original already, it would actually be a nice starting point for this. I understand Jeff Roberson has been doing some initial looking at NUMA, but more from a memory placement and less from a scheduling perspective? Robert N M Watson Computer Laboratory University of Cambridge > > You should probably tell us a little more about yourself: > > What kind of student? Graduate? Undergraduate? > Are you in a CS program or some other engineering program? > > Do you use FreeBSD? How long have you used it? > What do you do with it? > > Have you read Kirk McKusick's book on FreeBSD internals? > > Have you built and installed a FreeBSD system from source code? > > Have you taken classes on OS internals? > > How much C programming have you done? > > What areas of FreeBSD have you had the most problems with? > How would you make those areas better? > > Tim Kientzle > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 17:19:36 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 867B51065677; Thu, 26 Feb 2009 17:19:36 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (h-66-166-149-52.snvacaid.covad.net [66.166.149.52]) by mx1.freebsd.org (Postfix) with ESMTP id 489038FC25; Thu, 26 Feb 2009 17:19:36 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: (from root@localhost) by monday.kientzle.com (8.14.3/8.14.3) id n1QHJZN2018638; Thu, 26 Feb 2009 09:19:35 -0800 (PST) (envelope-from kientzle@freebsd.org) Received: from [10.123.2.23] (10.123.1.2 [10.123.1.2]) by monday.kientzle.com with SMTP id 3jxmph5uhxnmnp5bm4x2zukuu2; Thu, 26 Feb 2009 09:19:35 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <49A6CF27.3000203@freebsd.org> Date: Thu, 26 Feb 2009 09:19:35 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: <49A5D6FC.1090800@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Siddharth Prakash Singh , freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 17:19:37 -0000 Robert Watson wrote: > On Wed, 25 Feb 2009, Tim Kientzle wrote: > >>> I have not gone through the process scheduler code of Free BSD. >>> Hence, I am not yet aware about the current support for Multicore >>> Architectures. >> >> Since you posted to a lot of different lists, I think you probably >> don't already use FreeBSD. (If you did, why would you post to NetBSD >> and DragonflyBSD lists?) Scheduler work is quite complex and >> interacts heavily with the rest of the system; it may not be a good >> choice for someone who doesn't already have a lot of experience with >> FreeBSD. > > All the things you say are true, but let's not be too hard on the new > guy, however -- many of our GSoC students don't have previous FreeBSD > kernel-hacking experience. However, it does mean that they have to pick > project ideas that are well-suited to a significant warmup and > investigation period on the front end of the project. I apologize to Siddharth and others if I came off overly harsh. My intention was to caution him that he should plan for a lot of work prior to GSoC if he wants to tackle something that's at the core of the OS like this. > I'm also not convinced that a scheduler project along these lines would > be the most successful, but I wonder if a more experimental-spin > proposal for looking at how to investigate poor scheduling decisions > using dtrace, instrumentation and metrics to help us understand > performance on NUMA systems, and exploring the impact of heuristics > might go a long way. That's a good idea. The thing that's always impressed me about scheduling work is how very difficult it is to test. It's easy to change the scheduler code; it's much harder to measure whether those changes have made the scheduler better or not. Some testing support would help. Ideally, something non-intrusive that could be easily run on a lot of different machines so as to collect better information about the impacts of scheduler changes: * Load balancing: How effectively are all cores being used? * CPU switching: What percentage of the time does a thread stay on the same core? * NUMA statistics: How often does a thread get scheduled on a different processor from it's allocated memory? * Priority inversion: How often is a higher-priority thread idle while a lower-priority thread is running? A student who built such a tool and then ran some tests with a variety of hardware and workloads could really do a lot to advance scheduler development. Eventually, turning such a tool into something that anyone could run and upload data to a central collection site could be a huge advance. Certainly something to think about... Tim From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 17:24:22 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E12310658B6 for ; Thu, 26 Feb 2009 17:24:22 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.183]) by mx1.freebsd.org (Postfix) with ESMTP id DB74C8FC19 for ; Thu, 26 Feb 2009 17:24:21 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: by el-out-1112.google.com with SMTP id r27so719915ele.13 for ; Thu, 26 Feb 2009 09:24:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LJcXcEEBT5r3FCVtwwYnfvh8EeAtMLsQYBvF6ZDsVkA=; b=pyNEt1bP1WTKOxDtMq30Nbnrgk/IyQOxqh5gLz0KQxdWaQ+8X479zx9lnezggngB4W Cqh9tjwBL8Bl1tbq210eALUtlhXTnCjc7iYc/9+RDoavcn9w0Z01Wslm1GZqLCLXMHVS A4Kd9/D8me/eR6QBcaabfJtjmcGgXSxkrs9o0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=i2j6LSGbTm44PEkBNABG09m88o759cukoqjiquMR0nK4A064HF3hBfb2quODDGWWvp 47rQ2YEP6s1TW6TBsb5nBF+7/9RImQ5fY/4op6ANjuAQP5GfJnGcDxYNT47RaPI1zJtp y2iciWjidmOqwVR7w2+nuJRg/AFPUvdHLARCU= MIME-Version: 1.0 Received: by 10.90.94.15 with SMTP id r15mr797811agb.19.1235669061182; Thu, 26 Feb 2009 09:24:21 -0800 (PST) In-Reply-To: <49A6CF27.3000203@freebsd.org> References: <49A5D6FC.1090800@freebsd.org> <49A6CF27.3000203@freebsd.org> Date: Thu, 26 Feb 2009 09:24:20 -0800 Message-ID: <7d6fde3d0902260924r45ebb7c8i46cd6daf43a8171d@mail.gmail.com> From: Garrett Cooper To: Tim Kientzle Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Siddharth Prakash Singh , Robert Watson , freebsd-hackers@freebsd.org Subject: Re: Google SoC 2009 Idea X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 17:24:24 -0000 On Thu, Feb 26, 2009 at 9:19 AM, Tim Kientzle wrote: > Robert Watson wrote: >> >> On Wed, 25 Feb 2009, Tim Kientzle wrote: >> >>>> I have not gone through the process scheduler code of Free BSD. Hence,= I >>>> am not yet aware about the current support for Multicore Architectures= . >>> >>> Since you posted to a lot of different lists, I think you probably don'= t >>> already use FreeBSD. (If you did, why would you post to NetBSD and >>> DragonflyBSD lists?) =A0Scheduler work is quite complex and interacts h= eavily >>> with the rest of the system; it may not be a good choice for someone wh= o >>> doesn't already have a lot of experience with FreeBSD. >> >> All the things you say are true, but let's not be too hard on the new gu= y, >> however -- many of our GSoC students don't have previous FreeBSD >> kernel-hacking experience. =A0However, it does mean that they have to pi= ck >> project ideas that are well-suited to a significant warmup and investiga= tion >> period on the front end of the project. > > I apologize to Siddharth and others if I came off overly > harsh. =A0My intention was to caution him that he should > plan for a lot of work prior to GSoC if he wants to > tackle something that's at the core of the OS like this. > >> I'm also not convinced that a scheduler project along these lines would = be >> the most successful, but I wonder if a more experimental-spin proposal f= or >> looking at how to investigate poor scheduling decisions using dtrace, >> instrumentation and metrics to help us understand performance on NUMA >> systems, and exploring the impact of heuristics might go a long way. > > That's a good idea. =A0The thing that's always impressed > me about scheduling work is how very difficult it is to > test. =A0It's easy to change the scheduler code; it's > much harder to measure whether those changes have > made the scheduler better or not. > > Some testing support would help. =A0Ideally, something > non-intrusive that could be easily run on a lot > of different machines so as to collect better information > about the impacts of scheduler changes: > =A0* Load balancing: =A0How effectively are all cores being used? > =A0* CPU switching: =A0What percentage of the time does a thread > stay on the same core? > =A0* NUMA statistics: =A0How often does a thread get scheduled on a diffe= rent > processor from it's allocated memory? > =A0* Priority inversion: =A0How often is a higher-priority thread > idle while a lower-priority thread is running? > > A student who built such a tool and then ran some tests > with a variety of hardware and workloads could really > do a lot to advance scheduler development. =A0Eventually, > turning such a tool into something that anyone could run > and upload data to a central collection site could be > a huge advance. Speaking from experience, this is the way to go. If you don't do this you'll end up producing a potential black hole in terms of time and resources, which doesn't help your reputation on the project. Some food for thought. Cheers, -Garrett From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 18:07:58 2009 Return-Path: Delivered-To: hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 633B2106564A for ; Thu, 26 Feb 2009 18:07:58 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id 02B738FC17 for ; Thu, 26 Feb 2009 18:07:58 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id DF70F1CDE5; Thu, 26 Feb 2009 19:07:56 +0100 (CET) Date: Thu, 26 Feb 2009 19:07:56 +0100 From: Ed Schouten To: hackers@FreeBSD.org Message-ID: <20090226180756.GX19161@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="nKvJs6ze6az+4fwY" Content-Disposition: inline User-Agent: Mutt/1.5.19 (2009-01-05) Cc: Subject: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 18:07:58 -0000 --nKvJs6ze6az+4fwY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello all, As you may have read some days ago, work has started to make the FreeBSD base system compile better with clang, the BSD licensed C compiler from the LLVM project. One of the reasons why we can't compile the base system yet, is because some applications in the base system (keyserv, newkey, chkey, libtelnet) won't compile, because a library they depend (libmp)on has a function called pow(). By default, LLVM has a built-in prototype of pow(), similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The manual page also mentions this issue. After some talking on IRC, I think the best solution would be to rename all functions in libmp. Even though this may sound very awful at first, it seems the competition has done this as well: http://docs.sun.com/app/docs/doc/819-2246/mp-3mp?a=3Dview I'm not saying that if the Solaris developers jump off a cliff, we should do the same, but looking at the amount of applications that depend on libmp (almost none), I think it's the only definitive solution. So this is the patch I propose to commit to SVN one of these days: http://80386.nl/pub/mp.diff Because this also reduces some warnings when compiling stuff with GCC, I've increased WARNS in various Makefiles. I've also increased the SHLIB_MAJOR and __FreeBSD_version. Any comments? --=20 Ed Schouten WWW: http://80386.nl/ --nKvJs6ze6az+4fwY Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmm2nwACgkQ52SDGA2eCwWZvgCfYyJdyqMz5UzrAVrDY+r9bpCz HUcAni1z3hAWoNlBlXuX2PMvOlmeL3wp =43g2 -----END PGP SIGNATURE----- --nKvJs6ze6az+4fwY-- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 18:13:00 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F2FE106564A for ; Thu, 26 Feb 2009 18:13:00 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail16.syd.optusnet.com.au (mail16.syd.optusnet.com.au [211.29.132.197]) by mx1.freebsd.org (Postfix) with ESMTP id 1F3448FC1D for ; Thu, 26 Feb 2009 18:12:59 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-216-167.belrs3.nsw.optusnet.com.au [122.106.216.167]) by mail16.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n1QICQAL015263 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Feb 2009 05:12:28 +1100 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n1QICP2F070598; Fri, 27 Feb 2009 05:12:25 +1100 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n1QICPW6070597; Fri, 27 Feb 2009 05:12:25 +1100 (EST) (envelope-from peter) Date: Fri, 27 Feb 2009 05:12:25 +1100 From: Peter Jeremy To: Ed Schouten Message-ID: <20090226181225.GA3540@server.vk2pj.dyndns.org> References: <49A4B9ED.5040705@telenix.org> <20090225065308.GO19161@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline In-Reply-To: <20090225065308.GO19161@hoeg.nl> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.19 (2009-01-05) Cc: FreeBSD Hackers , Chuck Robey Subject: Re: x11 status X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 18:13:01 -0000 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Feb-25 07:53:08 +0100, Ed Schouten wrote: >The XFree86 project has been dying ever since almost all the active >development moved to the Xorg-project. Xorg has many new features that >XFree86 doesn't have, like hardware compositing and improved device >detection. And along the way, they've dropped things like integration testing, avoiding regressions and avoiding POLA violations. >> latest cvs image from Xfree86, and it built FAR easier that xorg, far >> faster, far simpler to configure ... > >Why should it matter how easy it is to build a piece of software? You >can just run `make -C /usr/ports/x11/xorg install clean' or `pkg_add -r >xorg'. Note that Chuck also mentioned faster (the conversion from imake to configure added something like 30% to the time to build X.org for absolutely no benefit - some pieces of X.org now take 4 times as long to configure as to build) and easier to configure. Whilst the ease of building a port doesn't really affect the end user, it does affect the port maintainer - a port that needs lots of tender care and feeding will lead to more rapid maintainer burnout. --=20 Peter Jeremy --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) iEYEARECAAYFAkmm24kACgkQ/opHv/APuIfgtQCggnm9MsYPOB/qxVAyL0D18CRu 4PsAoKROsm6tYoreYVnTB99fB9dtqMSg =ecl0 -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0-- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 18:18:39 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A12411065670 for ; Thu, 26 Feb 2009 18:18:39 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 5C08A8FC1D for ; Thu, 26 Feb 2009 18:18:39 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n1QIIGPo015222; Thu, 26 Feb 2009 13:18:16 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Thu, 26 Feb 2009 13:18:17 -0500 (EST) Date: Thu, 26 Feb 2009 13:18:16 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Ed Schouten In-Reply-To: <20090226180756.GX19161@hoeg.nl> Message-ID: References: <20090226180756.GX19161@hoeg.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: hackers@freebsd.org Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 18:18:40 -0000 On Thu, 26 Feb 2009, Ed Schouten wrote: > Hello all, > > As you may have read some days ago, work has started to make the FreeBSD > base system compile better with clang, the BSD licensed C compiler from > the LLVM project. > > One of the reasons why we can't compile the base system yet, is because > some applications in the base system (keyserv, newkey, chkey, libtelnet) > won't compile, because a library they depend (libmp)on has a function > called pow(). By default, LLVM has a built-in prototype of pow(), > similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The > manual page also mentions this issue. > > After some talking on IRC, I think the best solution would be to rename > all functions in libmp. Even though this may sound very awful at first, > it seems the competition has done this as well: > > http://docs.sun.com/app/docs/doc/819-2246/mp-3mp?a=view > > I'm not saying that if the Solaris developers jump off a cliff, we > should do the same, but looking at the amount of applications that > depend on libmp (almost none), I think it's the only definitive > solution. > > So this is the patch I propose to commit to SVN one of these days: > > http://80386.nl/pub/mp.diff > > Because this also reduces some warnings when compiling stuff with GCC, > I've increased WARNS in various Makefiles. I've also increased the > SHLIB_MAJOR and __FreeBSD_version. Why don't you add symbol versioning to libmp, so that old binaries will still work, but new ones will get the new symbols by default. Hmm, will that work without bumping SHLIB_MAJOR? You might want to play around with it and see. -- DE From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 18:25:44 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B94C1065670; Thu, 26 Feb 2009 18:25:44 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id 1F7478FC16; Thu, 26 Feb 2009 18:25:44 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 818B41CDE5; Thu, 26 Feb 2009 19:25:43 +0100 (CET) Date: Thu, 26 Feb 2009 19:25:43 +0100 From: Ed Schouten To: Daniel Eischen Message-ID: <20090226182543.GY19161@hoeg.nl> References: <20090226180756.GX19161@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4nn+A2p41ba1mxGd" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Cc: hackers@freebsd.org Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 18:25:44 -0000 --4nn+A2p41ba1mxGd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Daniel Eischen wrote: > Why don't you add symbol versioning to libmp, so that old > binaries will still work, but new ones will get the new > symbols by default. Hmm, will that work without bumping > SHLIB_MAJOR? You might want to play around with it and > see. Well, even without symbol versioning this could be done, by just making a __strong_reference() between the symbols, but I decided not to do so. I think solutions like these are perfect when just renaming/removing a couple of symbols, but because we're basically touching everything, I thought we'd better just use the old approach. --=20 Ed Schouten WWW: http://80386.nl/ --4nn+A2p41ba1mxGd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmm3qcACgkQ52SDGA2eCwVAVACfUiDVlfc8BEVoaUOFYzLx/Yhc cXIAniLcU9T0ls6RJbdLDYdq3k/KmLLV =Q2+Z -----END PGP SIGNATURE----- --4nn+A2p41ba1mxGd-- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 18:31:15 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79C3F1065670 for ; Thu, 26 Feb 2009 18:31:15 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 375B78FC0A for ; Thu, 26 Feb 2009 18:31:14 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n1QIUukl023421; Thu, 26 Feb 2009 13:30:56 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Thu, 26 Feb 2009 13:30:56 -0500 (EST) Date: Thu, 26 Feb 2009 13:30:56 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Ed Schouten In-Reply-To: <20090226182543.GY19161@hoeg.nl> Message-ID: References: <20090226180756.GX19161@hoeg.nl> <20090226182543.GY19161@hoeg.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: hackers@freebsd.org Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 18:31:15 -0000 On Thu, 26 Feb 2009, Ed Schouten wrote: > * Daniel Eischen wrote: >> Why don't you add symbol versioning to libmp, so that old >> binaries will still work, but new ones will get the new >> symbols by default. Hmm, will that work without bumping >> SHLIB_MAJOR? You might want to play around with it and >> see. > > Well, even without symbol versioning this could be done, by just making > a __strong_reference() between the symbols, but I decided not to do so. > I think solutions like these are perfect when just renaming/removing a > couple of symbols, but because we're basically touching everything, I > thought we'd better just use the old approach. Well, as long as you're in there, maybe you should add symbol versioning anyway, even after a library version bump. Seems like it would be easy since there aren't that many symbols. -- DE From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 18:40:22 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFD57106566C; Thu, 26 Feb 2009 18:40:22 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id 72E328FC17; Thu, 26 Feb 2009 18:40:22 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id C49D01CDE5; Thu, 26 Feb 2009 19:40:21 +0100 (CET) Date: Thu, 26 Feb 2009 19:40:21 +0100 From: Ed Schouten To: Daniel Eischen Message-ID: <20090226184021.GZ19161@hoeg.nl> References: <20090226180756.GX19161@hoeg.nl> <20090226182543.GY19161@hoeg.nl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yBbBYFH0ZHvzMoI/" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Cc: hackers@freebsd.org Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 18:40:23 -0000 --yBbBYFH0ZHvzMoI/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Daniel Eischen wrote: > Well, as long as you're in there, maybe you should add > symbol versioning anyway, even after a library version > bump. Seems like it would be easy since there aren't > that many symbols. I assume I should just mark all symbols with version FBSD_1.1? If so, the following patch should be good enough: http://80386.nl/pub/mp.diff --=20 Ed Schouten WWW: http://80386.nl/ --yBbBYFH0ZHvzMoI/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmm4hUACgkQ52SDGA2eCwWmyQCfbk1CvgA1dIIG1L2IiokLO2uB pvgAnj0SHjznLFnbAQoIypWi9iOST+73 =Z/wx -----END PGP SIGNATURE----- --yBbBYFH0ZHvzMoI/-- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 20:10:57 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4F661065687 for ; Thu, 26 Feb 2009 20:10:57 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from QMTA08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by mx1.freebsd.org (Postfix) with ESMTP id 603E18FC13 for ; Thu, 26 Feb 2009 20:10:57 +0000 (UTC) (envelope-from alex-goncharov@comcast.net) Received: from OMTA09.westchester.pa.mail.comcast.net ([76.96.62.20]) by QMTA08.westchester.pa.mail.comcast.net with comcast id LjXk1b00z0SCNGk58jxjwp; Thu, 26 Feb 2009 19:57:43 +0000 Received: from daland.home ([24.34.211.11]) by OMTA09.westchester.pa.mail.comcast.net with comcast id Ljxi1b00H0FJTGg3VjxiD0; Thu, 26 Feb 2009 19:57:43 +0000 Received: from algo by daland.home with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1LcmMX-000Cp1-0P; Thu, 26 Feb 2009 14:57:41 -0500 From: Alex Goncharov To: Peter Jeremy In-reply-to: <20090226181225.GA3540@server.vk2pj.dyndns.org> (message from Peter Jeremy on Fri, 27 Feb 2009 05:12:25 +1100) References: <49A4B9ED.5040705@telenix.org> <20090225065308.GO19161@hoeg.nl> <20090226181225.GA3540@server.vk2pj.dyndns.org> Message-Id: Sender: Alex Goncharov Date: Thu, 26 Feb 2009 14:57:41 -0500 Cc: ed@80386.nl, chuckr@telenix.org, freebsd-hackers@freebsd.org Subject: Re: x11 status X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alex Goncharov List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 20:10:58 -0000 ,--- You/Peter (Fri, 27 Feb 2009 05:12:25 +1100) ----* | And along the way, they've dropped things like integration testing, | avoiding regressions and avoiding POLA violations. Since I don't care about the new X anymore, I can afford to express my opinion bluntly: the Xorg we have in ports now is a disaster. This opinion was arrived to at the cost of more than two weeks undoing the damage to my systems under the circumstances not conductive for such activities. | >> latest cvs image from Xfree86, and it built FAR easier that xorg, | >> faster, far simpler to configure ... | > | >Why should it matter how easy it is to build a piece of software? You | >can just run `make -C /usr/ports/x11/xorg install clean' or `pkg_add -r | >xorg'. | | Note that Chuck also mentioned faster (the conversion from imake to | configure added something like 30% to the time to build X.org for | absolutely no benefit - some pieces of X.org now take 4 times as long | to configure as to build) and easier to configure. | | Whilst the ease of building a port doesn't really affect the end | user, I strongly disagree: a FreeBSD user is almost by definition somebody who ultimately turns from using built packages to building ports from source, with options of personal preference. So, how things are done build-wise, does affect me, big time. If the only option to get the contributed (ports) software were using packages, I'd be using Debian, not FreeBSD. I have no desire to have HAL on my systems, for example, and FreeBSD had been giving me the option of not having it -- just build it with an appropriate option in /etc/make.conf. And other such things. Struggling with the Xorg 1.5 unfortunate upgrade, and examining the ports make files for Xorg/Gnome moved me to the ultimate decision: don't try to comprehend this mess and stick with something that works. I rolled back everything x11 to "xorg-server 1.4.2" and have no plans to upgrade it -- ever, on any of my systems: the old one works, perhaps not perfectly, but predictably, and why would I need a new one? So, for the last month I've been doing weekly rebuilds of ports with everything upgraded -- other that the /usr/ports/x11* trees, which will be frozen until I see that other people stop reporting serious Xorg problems, which may well never happen. This is a testament to the greatness of the ports system and an illustration to my claim: building a port does affect the end user. -- Alex -- alex-goncharov@comcast.net -- From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 20:40:36 2009 Return-Path: Delivered-To: hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D25EB1065672 for ; Thu, 26 Feb 2009 20:40:36 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (ZIM.MIT.EDU [18.95.3.101]) by mx1.freebsd.org (Postfix) with ESMTP id 94CE98FC1F for ; Thu, 26 Feb 2009 20:40:36 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (localhost [127.0.0.1]) by zim.MIT.EDU (8.14.3/8.14.2) with ESMTP id n1QKghx9096333; Thu, 26 Feb 2009 15:42:43 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by zim.MIT.EDU (8.14.3/8.14.2/Submit) id n1QKghM2096332; Thu, 26 Feb 2009 15:42:43 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Thu, 26 Feb 2009 15:42:43 -0500 From: David Schultz To: Ed Schouten Message-ID: <20090226204243.GA96251@zim.MIT.EDU> Mail-Followup-To: Ed Schouten , hackers@FreeBSD.ORG References: <20090226180756.GX19161@hoeg.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090226180756.GX19161@hoeg.nl> Cc: hackers@FreeBSD.ORG Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 20:40:37 -0000 On Thu, Feb 26, 2009, Ed Schouten wrote: > One of the reasons why we can't compile the base system yet, is because > some applications in the base system (keyserv, newkey, chkey, libtelnet) > won't compile, because a library they depend (libmp)on has a function > called pow(). By default, LLVM has a built-in prototype of pow(), > similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The > manual page also mentions this issue. I think most apps that used to use libmp have transitioned to libgmp, so I don't have much of an opinion on this change... However, if the compiler as a builtin for the math.h-style pow() function, and the builtin causes it to choke even when math.h isn't #included, that's a bug in the compiler. The people who are proposing that we make the base system LLVM-compatible should be more forceful in insisting that LLVM be fixed. ;-) What do the LLVM folks propose to do about all the (perfectly legal) programs out there that have a variable called 'exp'? From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 20:50:29 2009 Return-Path: Delivered-To: hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6CB2106566B for ; Thu, 26 Feb 2009 20:50:29 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 1BE6B8FC12 for ; Thu, 26 Feb 2009 20:50:28 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 26 Feb 2009 20:50:27 -0000 Received: from p54A3E686.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.230.134] by mail.gmx.net (mp071) with SMTP; 26 Feb 2009 21:50:27 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX19K5qovzoNKJnPPFwvAatd6L9YT8Evhbgn+XiYn0F kcF99HpEwtDbaQ Message-ID: <49A70092.6030601@gmx.de> Date: Thu, 26 Feb 2009 21:50:26 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Ed Schouten , hackers@FreeBSD.ORG References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> In-Reply-To: <20090226204243.GA96251@zim.MIT.EDU> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.64 Cc: Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 20:50:30 -0000 David Schultz schrieb: > On Thu, Feb 26, 2009, Ed Schouten wrote: >> One of the reasons why we can't compile the base system yet, is because >> some applications in the base system (keyserv, newkey, chkey, libtelnet) >> won't compile, because a library they depend (libmp)on has a function >> called pow(). By default, LLVM has a built-in prototype of pow(), >> similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The >> manual page also mentions this issue. > > I think most apps that used to use libmp have transitioned to > libgmp, so I don't have much of an opinion on this change... > > However, if the compiler as a builtin for the math.h-style pow() > function, and the builtin causes it to choke even when math.h > isn't #included, that's a bug in the compiler. The people who are > proposing that we make the base system LLVM-compatible should be > more forceful in insisting that LLVM be fixed. ;-) What do the LLVM > folks propose to do about all the (perfectly legal) programs out > there that have a variable called 'exp'? No, it's invalid code to have a function named pow() in a hosted environment which is not /The/ pow(). Having a *local* variable named exp is fine, because this declaration shadows the function. A *global* variable on the other hand is not allowed. From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 21:02:31 2009 Return-Path: Delivered-To: hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A26010656C2 for ; Thu, 26 Feb 2009 21:02:31 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id EC4678FC17 for ; Thu, 26 Feb 2009 21:02:30 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 26 Feb 2009 21:02:29 -0000 Received: from p54A3E686.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.230.134] by mail.gmx.net (mp070) with SMTP; 26 Feb 2009 22:02:29 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1/oRDVESLroiFEPgXW+KOyvXmvK4ScR6gXHNI0CBL UPkJUpPTMg4K28 Message-ID: <49A70364.1020707@gmx.de> Date: Thu, 26 Feb 2009 22:02:28 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Ed Schouten , hackers@FreeBSD.ORG References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> <49A70092.6030601@gmx.de> In-Reply-To: <49A70092.6030601@gmx.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.55 Cc: Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 21:02:32 -0000 Christoph Mallon schrieb: > David Schultz schrieb: >> On Thu, Feb 26, 2009, Ed Schouten wrote: >>> One of the reasons why we can't compile the base system yet, is because >>> some applications in the base system (keyserv, newkey, chkey, libtelnet) >>> won't compile, because a library they depend (libmp)on has a function >>> called pow(). By default, LLVM has a built-in prototype of pow(), >>> similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The >>> manual page also mentions this issue. >> >> I think most apps that used to use libmp have transitioned to >> libgmp, so I don't have much of an opinion on this change... >> >> However, if the compiler as a builtin for the math.h-style pow() >> function, and the builtin causes it to choke even when math.h >> isn't #included, that's a bug in the compiler. The people who are >> proposing that we make the base system LLVM-compatible should be >> more forceful in insisting that LLVM be fixed. ;-) What do the LLVM >> folks propose to do about all the (perfectly legal) programs out >> there that have a variable called 'exp'? > > No, it's invalid code to have a function named pow() in a hosted > environment which is not /The/ pow(). > Having a *local* variable named exp is fine, because this declaration > shadows the function. A *global* variable on the other hand is not allowed. Just a hint, why you really mustn't use global names which are reserved by the standard: double pow(double x, double y) { abort(); } int main(void) { printf("%f\n", pow(10., 2.)); return 0; } %gcc -w bla.c %./a.out 100.000000 % Yes, GCC does that and it's perfectly valid. From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 21:06:09 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC569106568A for ; Thu, 26 Feb 2009 21:06:09 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.10]) by mx1.freebsd.org (Postfix) with ESMTP id 66D9C8FC1A for ; Thu, 26 Feb 2009 21:06:09 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.14.3/8.14.3/NETPLEX) with ESMTP id n1QL5oGQ027377; Thu, 26 Feb 2009 16:05:51 -0500 (EST) X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.0 (mail.netplex.net [204.213.176.10]); Thu, 26 Feb 2009 16:05:51 -0500 (EST) Date: Thu, 26 Feb 2009 16:05:50 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Ed Schouten In-Reply-To: <20090226184021.GZ19161@hoeg.nl> Message-ID: References: <20090226180756.GX19161@hoeg.nl> <20090226182543.GY19161@hoeg.nl> <20090226184021.GZ19161@hoeg.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: hackers@freebsd.org Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 21:06:09 -0000 On Thu, 26 Feb 2009, Ed Schouten wrote: > * Daniel Eischen wrote: >> Well, as long as you're in there, maybe you should add >> symbol versioning anyway, even after a library version >> bump. Seems like it would be easy since there aren't >> that many symbols. > > I assume I should just mark all symbols with version FBSD_1.1? If so, > the following patch should be good enough: > > http://80386.nl/pub/mp.diff Yeah, looks about right. That was easy :-) -- DE From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 22:11:54 2009 Return-Path: Delivered-To: hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB66E1065672 for ; Thu, 26 Feb 2009 22:11:54 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (ZIM.MIT.EDU [18.95.3.101]) by mx1.freebsd.org (Postfix) with ESMTP id 50BCB8FC14 for ; Thu, 26 Feb 2009 22:11:54 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (localhost [127.0.0.1]) by zim.MIT.EDU (8.14.3/8.14.2) with ESMTP id n1QME3Zx096867; Thu, 26 Feb 2009 17:14:03 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by zim.MIT.EDU (8.14.3/8.14.2/Submit) id n1QME3SM096866; Thu, 26 Feb 2009 17:14:03 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Thu, 26 Feb 2009 17:14:03 -0500 From: David Schultz To: Christoph Mallon Message-ID: <20090226221403.GA96580@zim.MIT.EDU> Mail-Followup-To: Christoph Mallon , Ed Schouten , hackers@FreeBSD.ORG References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> <49A70092.6030601@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49A70092.6030601@gmx.de> Cc: Ed Schouten , hackers@FreeBSD.ORG Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 22:11:55 -0000 On Thu, Feb 26, 2009, Christoph Mallon wrote: > David Schultz schrieb: > >On Thu, Feb 26, 2009, Ed Schouten wrote: > >>One of the reasons why we can't compile the base system yet, is because > >>some applications in the base system (keyserv, newkey, chkey, libtelnet) > >>won't compile, because a library they depend (libmp)on has a function > >>called pow(). By default, LLVM has a built-in prototype of pow(), > >>similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The > >>manual page also mentions this issue. > > > >I think most apps that used to use libmp have transitioned to > >libgmp, so I don't have much of an opinion on this change... > > > >However, if the compiler as a builtin for the math.h-style pow() > >function, and the builtin causes it to choke even when math.h > >isn't #included, that's a bug in the compiler. The people who are > >proposing that we make the base system LLVM-compatible should be > >more forceful in insisting that LLVM be fixed. ;-) What do the LLVM > >folks propose to do about all the (perfectly legal) programs out > >there that have a variable called 'exp'? > > No, it's invalid code to have a function named pow() in a hosted > environment which is not /The/ pow(). > Having a *local* variable named exp is fine, because this declaration > shadows the function. A *global* variable on the other hand is not allowed. The C standard makes no guarantees because it doesn't want to say much about system libraries or how apps are actually linked, but in practice people have found it very useful to do things like link against libraries with special debugging versions of malloc(), and in the past, developers have tried to ensure that this continues to work. (You can find some old threads in the archives.) Of course, people who do this need to take adequate precautions (e.g., linking their programs in the right order, using weak symbols where appropriate), but it does work, and it would be nice if the compiler didn't break it. As for gcc's math builtins, most of them are buggy. They fail to respect the dynamic rounding mode, fail to generate exceptions where appropriate, fail to respect FENV_ACCESS and other pragmas, etc. Also, the complex builtins use simplified formulas that don't get the right answers for complex numbers with inf/nan components. Try running some of the tests in tools/regression/lib/msun without -fno-builtin and see what happens ;-) From owner-freebsd-hackers@FreeBSD.ORG Thu Feb 26 22:26:40 2009 Return-Path: Delivered-To: hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C71E106566C for ; Thu, 26 Feb 2009 22:26:40 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 7D7C28FC08 for ; Thu, 26 Feb 2009 22:26:39 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 26 Feb 2009 22:26:38 -0000 Received: from p54A3E686.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.230.134] by mail.gmx.net (mp062) with SMTP; 26 Feb 2009 23:26:38 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX1/HIElGFYjHuBeubS+Bfm6XDREs76Y+FW7KAywCRR UnXlSyLLUxWmet Message-ID: <49A7171D.1060401@gmx.de> Date: Thu, 26 Feb 2009 23:26:37 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Christoph Mallon , Ed Schouten , hackers@FreeBSD.ORG References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> <49A70092.6030601@gmx.de> <20090226221403.GA96580@zim.MIT.EDU> In-Reply-To: <20090226221403.GA96580@zim.MIT.EDU> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.6 Cc: Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Feb 2009 22:26:40 -0000 David Schultz schrieb: > On Thu, Feb 26, 2009, Christoph Mallon wrote: >> David Schultz schrieb: >>> On Thu, Feb 26, 2009, Ed Schouten wrote: >>>> One of the reasons why we can't compile the base system yet, is because >>>> some applications in the base system (keyserv, newkey, chkey, libtelnet) >>>> won't compile, because a library they depend (libmp)on has a function >>>> called pow(). By default, LLVM has a built-in prototype of pow(), >>>> similar to GCC. Unlike GCC, LLVM raises a compiler error by default. The >>>> manual page also mentions this issue. >>> I think most apps that used to use libmp have transitioned to >>> libgmp, so I don't have much of an opinion on this change... >>> >>> However, if the compiler as a builtin for the math.h-style pow() >>> function, and the builtin causes it to choke even when math.h >>> isn't #included, that's a bug in the compiler. The people who are >>> proposing that we make the base system LLVM-compatible should be >>> more forceful in insisting that LLVM be fixed. ;-) What do the LLVM >>> folks propose to do about all the (perfectly legal) programs out >>> there that have a variable called 'exp'? >> No, it's invalid code to have a function named pow() in a hosted >> environment which is not /The/ pow(). >> Having a *local* variable named exp is fine, because this declaration >> shadows the function. A *global* variable on the other hand is not allowed. > > The C standard makes no guarantees because it doesn't want to say > much about system libraries or how apps are actually linked, but The C standard is very explicit which identifiers are reserved, see §7.1.3 > in practice people have found it very useful to do things like > link against libraries with special debugging versions of > malloc(), and in the past, developers have tried to ensure that > this continues to work. (You can find some old threads in the > archives.) Of course, people who do this need to take adequate > precautions (e.g., linking their programs in the right order, > using weak symbols where appropriate), but it does work, and it > would be nice if the compiler didn't break it. > > As for gcc's math builtins, most of them are buggy. They fail to > respect the dynamic rounding mode, fail to generate exceptions > where appropriate, fail to respect FENV_ACCESS and other pragmas, > etc. Also, the complex builtins use simplified formulas that don't > get the right answers for complex numbers with inf/nan components. > Try running some of the tests in tools/regression/lib/msun without > -fno-builtin and see what happens ;-) pow() is just an example. The compiler may do magic with any call which has semantics defined by the C standard in a hosted environment. From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 27 05:25:48 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8BE341065676 for ; Fri, 27 Feb 2009 05:25:48 +0000 (UTC) (envelope-from neldredge@math.ucsd.edu) Received: from euclid.ucsd.edu (euclid.ucsd.edu [132.239.145.52]) by mx1.freebsd.org (Postfix) with ESMTP id 6F87E8FC19 for ; Fri, 27 Feb 2009 05:25:48 +0000 (UTC) (envelope-from neldredge@math.ucsd.edu) Received: from zeno.ucsd.edu (zeno.ucsd.edu [132.239.145.22]) by euclid.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id n1R5Pmo21880 for ; Thu, 26 Feb 2009 21:25:48 -0800 (PST) Received: from localhost (neldredg@localhost) by zeno.ucsd.edu (8.11.7p3+Sun/8.11.7) with ESMTP id n1R5Pm205774 for ; Thu, 26 Feb 2009 21:25:48 -0800 (PST) X-Authentication-Warning: zeno.ucsd.edu: neldredg owned process doing -bs Date: Thu, 26 Feb 2009 21:25:47 -0800 (PST) From: Nate Eldredge X-X-Sender: neldredg@zeno.ucsd.edu To: freebsd-hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: portupgrade spurious skips X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2009 05:25:48 -0000 Hi folks, In the past few months I've noticed a bug in portupgrade. When I update my ports tree and do `portupgrade -a', often a few ports will be skipped, supposedly because another port on which they depend failed to install. However, the apparently failed port actually did not fail, and if I rerun `portupgrade -a', some of the skipped ports will install successfully without complaint. After enough iterations I can eventually get all of them. I'd like to file a PR about this, but it's a little bit tricky coming up with a test case, since the behavior depends on having outdated packages installed, and on the dependencies between them. Moreover, after I run `portupgrade -a' and notice the problem, the state of the installed packages has changed and the same packages aren't skipped the next time. So my question is whether anyone has ideas about how to construct a reasonable test case that could help me make this reproducible and easier to investigate. Any thoughts? Thanks in advance. -- Nate Eldredge neldredge@math.ucsd.edu From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 27 05:26:11 2009 Return-Path: Delivered-To: hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32765106566C for ; Fri, 27 Feb 2009 05:26:10 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (ZIM.MIT.EDU [18.95.3.101]) by mx1.freebsd.org (Postfix) with ESMTP id 18C198FC1D for ; Fri, 27 Feb 2009 05:26:09 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (localhost [127.0.0.1]) by zim.MIT.EDU (8.14.3/8.14.2) with ESMTP id n1R5SMYe098812; Fri, 27 Feb 2009 00:28:22 -0500 (EST) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by zim.MIT.EDU (8.14.3/8.14.2/Submit) id n1R5SL56098811; Fri, 27 Feb 2009 00:28:21 -0500 (EST) (envelope-from das@FreeBSD.ORG) Date: Fri, 27 Feb 2009 00:28:21 -0500 From: David Schultz To: Christoph Mallon Message-ID: <20090227052821.GA98527@zim.MIT.EDU> Mail-Followup-To: Christoph Mallon , Ed Schouten , hackers@FreeBSD.ORG References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> <49A70092.6030601@gmx.de> <20090226221403.GA96580@zim.MIT.EDU> <49A7171D.1060401@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49A7171D.1060401@gmx.de> Cc: Ed Schouten , hackers@FreeBSD.ORG Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2009 05:26:11 -0000 On Thu, Feb 26, 2009, Christoph Mallon wrote: > David Schultz schrieb: > >As for gcc's math builtins, most of them are buggy. They fail to > >respect the dynamic rounding mode, fail to generate exceptions > >where appropriate, fail to respect FENV_ACCESS and other pragmas, > >etc. Also, the complex builtins use simplified formulas that don't > >get the right answers for complex numbers with inf/nan components. > >Try running some of the tests in tools/regression/lib/msun without > >-fno-builtin and see what happens ;-) > > pow() is just an example. > The compiler may do magic with any call which has semantics defined by > the C standard in a hosted environment. Okay, so first, the world doesn't revolve around the strictest possible interpretation of the C standard. For example, FreeBSD has an extension such that `printf("%s", NULL)' prints "(null)" instead of having undefined behavior. But gcc translates this into `puts(NULL)', which once again has undefined behavior. You can put on your lawyer hat and counter that the beloved standard doesn't guarantee that any such thing will work, but that's a very contrarian attitude; the bottom line is that it's a POLA violation, and the extension worked just fine for many years. Second, the problems with the math builtins I cited above violate even a strict interpretation of the C standard. Third, this is a digression, and this is the last I'm going to say about it. :-) From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 27 06:13:03 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 766C21065673 for ; Fri, 27 Feb 2009 06:13:03 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from email1.allantgroup.com (email1.emsphone.com [199.67.51.115]) by mx1.freebsd.org (Postfix) with ESMTP id 30CD78FC1B for ; Fri, 27 Feb 2009 06:13:03 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by email1.allantgroup.com (8.14.0/8.14.0) with ESMTP id n1R5vdpO047984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 26 Feb 2009 23:57:39 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (smmsp@localhost [127.0.0.1]) by dan.emsphone.com (8.14.3/8.14.3) with ESMTP id n1R5vc7X069543 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 26 Feb 2009 23:57:39 -0600 (CST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.14.3/8.14.3/Submit) id n1R5vb1H069542; Thu, 26 Feb 2009 23:57:37 -0600 (CST) (envelope-from dan) Date: Thu, 26 Feb 2009 23:57:37 -0600 From: Dan Nelson To: Nate Eldredge Message-ID: <20090227055737.GF45976@dan.emsphone.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 7.1-STABLE User-Agent: Mutt/1.5.19 (2009-01-05) X-Virus-Scanned: ClamAV version 0.94.1, clamav-milter version 0.94.1 on email1.allantgroup.com X-Virus-Status: Clean X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (email1.allantgroup.com [199.67.51.78]); Thu, 26 Feb 2009 23:57:39 -0600 (CST) X-Scanned-By: MIMEDefang 2.45 Cc: freebsd-hackers@freebsd.org Subject: Re: portupgrade spurious skips X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2009 06:13:03 -0000 In the last episode (Feb 26), Nate Eldredge said: > In the past few months I've noticed a bug in portupgrade. When I update > my ports tree and do `portupgrade -a', often a few ports will be skipped, > supposedly because another port on which they depend failed to install. > However, the apparently failed port actually did not fail, and if I rerun > `portupgrade -a', some of the skipped ports will install successfully > without complaint. After enough iterations I can eventually get all of > them. > > I'd like to file a PR about this, but it's a little bit tricky coming up > with a test case, since the behavior depends on having outdated packages > installed, and on the dependencies between them. Moreover, after I run > `portupgrade -a' and notice the problem, the state of the installed > packages has changed and the same packages aren't skipped the next time. > So my question is whether anyone has ideas about how to construct a > reasonable test case that could help me make this reproducible and easier > to investigate. Any thoughts? "me too".. It seems to happen frequently when doing > 20 or so ports. Every week or so I upgrade old ports and don't have problems, but after a gnome or xorg update that ends up bumping the portrevision for half my installed ports, it always takes three or four "portupgrade -a" loops for everything to buid. If you've got ZFS, you can snapshot your filesystems, and if portupgrade fails, roll back to the snapshot and do it again to see if it happens on the same port a second time. Or if you know ruby, you could instrument the code that checks for port build errors and see if it's got a bug in it... -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 27 06:49:30 2009 Return-Path: Delivered-To: hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFE65106564A for ; Fri, 27 Feb 2009 06:49:30 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 3BA748FC19 for ; Fri, 27 Feb 2009 06:49:30 +0000 (UTC) (envelope-from christoph.mallon@gmx.de) Received: (qmail invoked by alias); 27 Feb 2009 06:49:28 -0000 Received: from p54A3E7C3.dip.t-dialin.net (EHLO tron.homeunix.org) [84.163.231.195] by mail.gmx.net (mp062) with SMTP; 27 Feb 2009 07:49:28 +0100 X-Authenticated: #1673122 X-Provags-ID: V01U2FsdGVkX18YS6URN/MYm0jbqPeK7h8VvQk2ymJGQNZAInytdG TR3POBcTQHb/uY Message-ID: <49A78CF7.8090606@gmx.de> Date: Fri, 27 Feb 2009 07:49:27 +0100 From: Christoph Mallon User-Agent: Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Christoph Mallon , Ed Schouten , hackers@FreeBSD.ORG References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> <49A70092.6030601@gmx.de> <20090226221403.GA96580@zim.MIT.EDU> <49A7171D.1060401@gmx.de> <20090227052821.GA98527@zim.MIT.EDU> In-Reply-To: <20090227052821.GA98527@zim.MIT.EDU> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.58 Cc: Subject: Re: Renaming all symbols in libmp(3) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2009 06:49:31 -0000 David Schultz schrieb: > On Thu, Feb 26, 2009, Christoph Mallon wrote: >> David Schultz schrieb: >>> As for gcc's math builtins, most of them are buggy. They fail to >>> respect the dynamic rounding mode, fail to generate exceptions >>> where appropriate, fail to respect FENV_ACCESS and other pragmas, >>> etc. Also, the complex builtins use simplified formulas that don't >>> get the right answers for complex numbers with inf/nan components. >>> Try running some of the tests in tools/regression/lib/msun without >>> -fno-builtin and see what happens ;-) >> pow() is just an example. >> The compiler may do magic with any call which has semantics defined by >> the C standard in a hosted environment. > > Okay, so first, the world doesn't revolve around the strictest > possible interpretation of the C standard. For example, FreeBSD So you haven't seen enough crashes and security problems due to sloppy coding in the past decades, yet? I don't agree with everything the standard says (e.g. it tells you that it's a bad idea to call a function strange_quark()), but there's no reason not to avoid a simple name clash. > has an extension such that `printf("%s", NULL)' prints "(null)" > instead of having undefined behavior. But gcc translates this into This *is* perfectly valid undefined behaviour. > `puts(NULL)', which once again has undefined behavior. You can put And this is, too. I prefer the crash variant (or the one with the demons flying out of the programmers nose), because I've seen quite some programs which showed me "(null)" where they should have printed something sensible and bugs (sadly) only seem to have a real chance of being fixed in a timely manner, when they are hard crashes. A program limping along with invalid data is very bad and could be a security problem, too - imagine a "(null)" in an sprintf()ed path or something. > on your lawyer hat and counter that the beloved standard doesn't > guarantee that any such thing will work, but that's a very > contrarian attitude; the bottom line is that it's a POLA > violation, and the extension worked just fine for many years. It's a POLA violation in the first place, to have a function named pow(), which does not the "real" pow() thing. > Second, the problems with the math builtins I cited above violate > even a strict interpretation of the C standard. GCC is buggy, but that's a totally different story. > Third, this is a digression, and this is the last I'm going to say > about it. :-) Me, too. From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 27 08:24:37 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F216F1065673 for ; Fri, 27 Feb 2009 08:24:37 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id B350C8FC16 for ; Fri, 27 Feb 2009 08:24:37 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n1R7pC0Z030854 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 26 Feb 2009 23:51:12 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n1R7pC6r030853; Thu, 26 Feb 2009 23:51:12 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA04566; Thu, 26 Feb 09 23:46:36 PST Date: Thu, 26 Feb 2009 23:46:22 -0800 From: perryh@pluto.rain.com To: christoph.mallon@gmx.de Message-Id: <49a79a4e.jj/fvw29lwxNJgz+%perryh@pluto.rain.com> References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> <49A70092.6030601@gmx.de> In-Reply-To: <49A70092.6030601@gmx.de> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: hosted, or not (Re: Renaming all symbols in libmp(3)) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2009 08:24:38 -0000 > >> By default, LLVM has a built-in prototype of pow(), similar to > >> GCC. Unlike GCC, LLVM raises a compiler error by default ... > ... it's invalid code to have a function named pow() > in a hosted environment which is not /The/ pow(). ^^^^^^^^^^^^^^^^^^^^^^^ I don't suppose LLVM supports a commmand-line switch to use embedded mode instead of hosted? From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 27 08:27:49 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3135F106566C for ; Fri, 27 Feb 2009 08:27:49 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id E0B178FC21 for ; Fri, 27 Feb 2009 08:27:48 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 8758D9CB121; Fri, 27 Feb 2009 09:24:33 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b7TMfhgUlTax; Fri, 27 Feb 2009 09:24:19 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id F1BA19CB169; Fri, 27 Feb 2009 09:24:18 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n1R8OIR7056529; Fri, 27 Feb 2009 09:24:18 +0100 (CET) (envelope-from rdivacky) Date: Fri, 27 Feb 2009 09:24:18 +0100 From: Roman Divacky To: perryh@pluto.rain.com Message-ID: <20090227082417.GA55567@freebsd.org> References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> <49A70092.6030601@gmx.de> <49a79a4e.jj/fvw29lwxNJgz+%perryh@pluto.rain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49a79a4e.jj/fvw29lwxNJgz+%perryh@pluto.rain.com> User-Agent: Mutt/1.4.2.3i Cc: hackers@freebsd.org, christoph.mallon@gmx.de Subject: Re: hosted, or not (Re: Renaming all symbols in libmp(3)) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2009 08:27:49 -0000 On Thu, Feb 26, 2009 at 11:46:22PM -0800, perryh@pluto.rain.com wrote: > > >> By default, LLVM has a built-in prototype of pow(), similar to > > >> GCC. Unlike GCC, LLVM raises a compiler error by default ... > > > ... it's invalid code to have a function named pow() > > in a hosted environment which is not /The/ pow(). > ^^^^^^^^^^^^^^^^^^^^^^^ > > I don't suppose LLVM supports a commmand-line switch to use embedded > mode instead of hosted? of course it does.... -ffreestanding From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 27 12:19:48 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 026E01065670 for ; Fri, 27 Feb 2009 12:19:48 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from redbull.bpaserver.net (redbullneu.bpaserver.net [213.198.78.217]) by mx1.freebsd.org (Postfix) with ESMTP id 825838FC0C for ; Fri, 27 Feb 2009 12:19:47 +0000 (UTC) (envelope-from alexander@leidinger.net) Received: from outgoing.leidinger.net (pD9E2E80C.dip.t-dialin.net [217.226.232.12]) by redbull.bpaserver.net (Postfix) with ESMTP id DD3FC2E1FE; Fri, 27 Feb 2009 13:19:39 +0100 (CET) Received: from webmail.leidinger.net (webmail.leidinger.net [192.168.1.102]) by outgoing.leidinger.net (Postfix) with ESMTP id 4855B1AFBAD; Fri, 27 Feb 2009 13:19:33 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=Leidinger.net; s=outgoing-alex; t=1235737173; bh=CSHnyZquxhpUjz3zvrI2K6XtwsK90g35h 4n3xXpBbm8=; h=Message-ID:Date:From:To:Cc:Subject:References: In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=p+HfqG9QPZ8S6SwGDce+KynqYl57oCgOAR6TXeSycQBBvayn/alGVFPdVx5khUwM4 xa+FfvcFSIzszM6MQu4i2f6jkC90wzJfkpDzkRzlif2jDeD40Sk6ZRPkokoYemFrSk6 Q8nEHQwD6//O3clDRLt8XXpjQfCdlyGbnX8+SGrHg6RbmFnkxTm4NxJvxG9/DSdRnRF 7mbRN+5y7EYxs9cQcHmNOFyRbakzX6FObP+yU7PF8A1rlwC3V5qSuPNNfwri9niq9LP spBUM7EcEDPG399IOOEIGhkjNIoVoPfPAjdp9TM42CssXCGOzNnSyZFZcBTZTxd/gsL WadBIq45Q== Received: (from www@localhost) by webmail.leidinger.net (8.14.3/8.13.8/Submit) id n1RCJWCJ006173; Fri, 27 Feb 2009 13:19:32 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde Framework) with HTTP; Fri, 27 Feb 2009 13:19:31 +0100 Message-ID: <20090227131931.18306giseysouk8w@webmail.leidinger.net> X-Priority: 3 (Normal) Date: Fri, 27 Feb 2009 13:19:31 +0100 From: Alexander Leidinger To: Dan Nelson References: <20090227055737.GF45976@dan.emsphone.com> In-Reply-To: <20090227055737.GF45976@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.3) / FreeBSD-8.0 X-BPAnet-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: DD3FC2E1FE.8E022 X-BPAnet-MailScanner: Found to be clean X-BPAnet-MailScanner-SpamCheck: not spam, ORDB-RBL, SpamAssassin (not cached, score=-13.504, required 6, BAYES_00 -15.00, DKIM_SIGNED 0.00, DKIM_VERIFIED -0.00, MIME_QP_LONG_LINE 1.40, RDNS_DYNAMIC 0.10) X-BPAnet-MailScanner-From: alexander@leidinger.net X-Spam-Status: No X-Mailman-Approved-At: Fri, 27 Feb 2009 12:25:51 +0000 Cc: Nate Eldredge , freebsd-hackers@freebsd.org Subject: Re: portupgrade spurious skips X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Feb 2009 12:19:48 -0000 Quoting Dan Nelson (from Thu, 26 Feb 2009 =20 23:57:37 -0600): > In the last episode (Feb 26), Nate Eldredge said: >> In the past few months I've noticed a bug in portupgrade. When I update >> my ports tree and do `portupgrade -a', often a few ports will be skipped, >> supposedly because another port on which they depend failed to install. >> However, the apparently failed port actually did not fail, and if I rerun >> `portupgrade -a', some of the skipped ports will install successfully >> without complaint. After enough iterations I can eventually get all of >> them. >> >> I'd like to file a PR about this, but it's a little bit tricky coming up >> with a test case, since the behavior depends on having outdated packages >> installed, and on the dependencies between them. Moreover, after I run >> `portupgrade -a' and notice the problem, the state of the installed >> packages has changed and the same packages aren't skipped the next time. >> So my question is whether anyone has ideas about how to construct a >> reasonable test case that could help me make this reproducible and easier >> to investigate. Any thoughts? > > "me too".. It seems to happen frequently when doing > 20 or so ports. > Every week or so I upgrade old ports and don't have problems, but after a > gnome or xorg update that ends up bumping the portrevision for half my > installed ports, it always takes three or four "portupgrade -a" loops for > everything to buid. > > If you've got ZFS, you can snapshot your filesystems, and if portupgrade > fails, roll back to the snapshot and do it again to see if it happens on t= he > same port a second time. Or if you know ruby, you could instrument the co= de > that checks for port build errors and see if it's got a bug in it... There's a more easy solution, pipe the output of portupgrade to a =20 logfile. This way you can have a look what happened with the port =20 which was reported as broken. Maybe there's a dependency missing, and =20 after updating other ports after the failure, this dependency was =20 satisfied so that the next run succeeds. Bye, Alexander. --=20 A squeegee by any other name wouldn't sound as funny. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 28 09:11:08 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3B6C106566B for ; Sat, 28 Feb 2009 09:11:08 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 8BB738FC18 for ; Sat, 28 Feb 2009 09:11:08 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id n1S9Aiv0036523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 28 Feb 2009 01:10:44 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id n1S9Aies036522; Sat, 28 Feb 2009 01:10:44 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA08268; Sat, 28 Feb 09 01:03:01 PST Date: Sat, 28 Feb 2009 01:02:44 -0800 From: perryh@pluto.rain.com To: ed@80386.nl, rdivacky@freebsd.org Message-Id: <49a8fdb4.47pe/BeTfmPBIr7P%perryh@pluto.rain.com> References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> <49A70092.6030601@gmx.de> <49a79a4e.jj/fvw29lwxNJgz+%perryh@pluto.rain.com> <20090227082417.GA55567@freebsd.org> In-Reply-To: <20090227082417.GA55567@freebsd.org> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org, christoph.mallon@gmx.de Subject: Re: hosted, or not (Re: Renaming all symbols in libmp(3)) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2009 09:11:09 -0000 Roman Divacky wrote: > On Thu, Feb 26, 2009 at 11:46:22PM -0800, perryh@pluto.rain.com wrote: > > > >> By default, LLVM has a built-in prototype of pow(), similar to > > > >> GCC. Unlike GCC, LLVM raises a compiler error by default ... > > > > > ... it's invalid code to have a function named pow() > > > in a hosted environment which is not /The/ pow(). > > ^^^^^^^^^^^^^^^^^^^^^^^ > > > > I don't suppose LLVM supports a commmand-line switch to use > > embedded mode instead of hosted? > > of course it does.... -ffreestanding So perhaps one solution would be to compile libmp with -ffreestanding? From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 28 09:24:57 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECBE1106564A; Sat, 28 Feb 2009 09:24:57 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [IPv6:2001:7b8:613:100::211]) by mx1.freebsd.org (Postfix) with ESMTP id 86FF68FC13; Sat, 28 Feb 2009 09:24:57 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id 945051CDE5; Sat, 28 Feb 2009 10:24:56 +0100 (CET) Date: Sat, 28 Feb 2009 10:24:56 +0100 From: Ed Schouten To: perryh@pluto.rain.com Message-ID: <20090228092456.GJ19161@hoeg.nl> References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> <49A70092.6030601@gmx.de> <49a79a4e.jj/fvw29lwxNJgz+%perryh@pluto.rain.com> <20090227082417.GA55567@freebsd.org> <49a8fdb4.47pe/BeTfmPBIr7P%perryh@pluto.rain.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4Cwqj9FHWD4ffUzp" Content-Disposition: inline In-Reply-To: <49a8fdb4.47pe/BeTfmPBIr7P%perryh@pluto.rain.com> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: hackers@freebsd.org, rdivacky@freebsd.org, christoph.mallon@gmx.de Subject: Re: hosted, or not (Re: Renaming all symbols in libmp(3)) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2009 09:24:58 -0000 --4Cwqj9FHWD4ffUzp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * perryh@pluto.rain.com wrote: > So perhaps one solution would be to compile libmp with -ffreestanding? And all applications that use . --=20 Ed Schouten WWW: http://80386.nl/ --4Cwqj9FHWD4ffUzp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkmpAugACgkQ52SDGA2eCwV0BgCeMVQDVS5cY09N9diq2CHCGDUx KwsAn2rS4k4fjd+q7H4kSzPBsHSZocl4 =B2jt -----END PGP SIGNATURE----- --4Cwqj9FHWD4ffUzp-- From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 28 09:47:07 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29CEF1065670 for ; Sat, 28 Feb 2009 09:47:07 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id D78A98FC14 for ; Sat, 28 Feb 2009 09:47:06 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id B17B69CB084; Sat, 28 Feb 2009 10:43:49 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z6gufVFkWhfm; Sat, 28 Feb 2009 10:43:47 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 6F5AC9CB121; Sat, 28 Feb 2009 10:43:47 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n1S9hleG061370; Sat, 28 Feb 2009 10:43:47 +0100 (CET) (envelope-from rdivacky) Date: Sat, 28 Feb 2009 10:43:47 +0100 From: Roman Divacky To: Ed Schouten Message-ID: <20090228094347.GA61328@freebsd.org> References: <20090226180756.GX19161@hoeg.nl> <20090226204243.GA96251@zim.MIT.EDU> <49A70092.6030601@gmx.de> <49a79a4e.jj/fvw29lwxNJgz+%perryh@pluto.rain.com> <20090227082417.GA55567@freebsd.org> <49a8fdb4.47pe/BeTfmPBIr7P%perryh@pluto.rain.com> <20090228092456.GJ19161@hoeg.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090228092456.GJ19161@hoeg.nl> User-Agent: Mutt/1.4.2.3i Cc: christoph.mallon@gmx.de, hackers@freebsd.org, perryh@pluto.rain.com Subject: Re: hosted, or not (Re: Renaming all symbols in libmp(3)) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2009 09:47:08 -0000 On Sat, Feb 28, 2009 at 10:24:56AM +0100, Ed Schouten wrote: > * perryh@pluto.rain.com wrote: > > So perhaps one solution would be to compile libmp with -ffreestanding? > > And all applications that use . which is a nonsense... please move forward From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 28 04:44:24 2009 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2E011065672 for ; Sat, 28 Feb 2009 04:44:24 +0000 (UTC) (envelope-from boris@brooknet.com.au) Received: from smtp.po.exetel.com.au (pecan.exetel.com.au [220.233.0.17]) by mx1.freebsd.org (Postfix) with ESMTP id 4679B8FC15 for ; Sat, 28 Feb 2009 04:44:24 +0000 (UTC) (envelope-from boris@brooknet.com.au) Received: from 243.169.233.220.exetel.com.au ([220.233.169.243] helo=[192.168.100.157]) by smtp.po.exetel.com.au with esmtp (Exim 4.68) (envelope-from ) id 1LdGko-00054n-M4 for hackers@freebsd.org; Sat, 28 Feb 2009 15:24:46 +1100 Message-Id: <8662C4CC-DE22-4D48-BF57-0CE19ECFEABD@brooknet.com.au> From: Sam Lawrance To: hackers@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sat, 28 Feb 2009 15:24:46 +1100 References: <20090227201947.GB24240@bcd.geek.com.au> X-Mailer: Apple Mail (2.930.3) X-Mailman-Approved-At: Sat, 28 Feb 2009 12:12:51 +0000 Cc: Subject: Fwd: Kernel conference Australia X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Feb 2009 04:44:25 -0000 Early days, this could be cool. Interested speakers might consider approaching their employers or the FreeBSD Foundation to obtain assistance. Begin forwarded message: > From: Daniel Carosone > Date: 28 February 2009 7:19:47 AM > To: current-users@netbsd.org, regional-au@netbsd.org > Subject: Kernel conference Australia > > Just spotted this go by my RSS, in case others are interested. > > http://ln-s.net/2vsw > > -- > Dan.