From owner-freebsd-smp@FreeBSD.ORG Thu Oct 11 17:29:33 2007 Return-Path: Delivered-To: freebsd-smp@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3310816A419 for ; Thu, 11 Oct 2007 17:29:33 +0000 (UTC) (envelope-from tching@arraynetworks.net) Received: from Exchange.arraynetworks.net (mail.arraynetworks.net [12.22.49.71]) by mx1.freebsd.org (Postfix) with ESMTP id 2672813C45D for ; Thu, 11 Oct 2007 17:29:33 +0000 (UTC) (envelope-from tching@arraynetworks.net) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 11 Oct 2007 10:17:30 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Supermicro H8DAE-2 support Thread-Index: AcgMKpicWqT/GnRzQqq26s+vJ5d+GA== From: "Thomas Ching" To: Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Supermicro H8DAE-2 support X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 17:29:33 -0000 Hi,=20 =20 I am a newbie to this so I apologize if I did not follow any protocol = that I am supposed to.=20 =20 I am porting FreeBSD 4.5 to this board and I am just wondering if anyone = has any information that I can read. I am really concerned about given = how new the board is and 4.5 would probably not run on it.=20 =20 It has to be 4.5 for legacy reasons. =20 Thanks Thomas No virus found in this outgoing message. Checked by AVG Free Edition.=20 Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM =20 From owner-freebsd-smp@FreeBSD.ORG Thu Oct 11 17:40:58 2007 Return-Path: Delivered-To: freebsd-smp@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5112516A46C for ; Thu, 11 Oct 2007 17:40:58 +0000 (UTC) (envelope-from tching@arraynetworks.net) Received: from Exchange.arraynetworks.net (mail.arraynetworks.net [12.22.49.71]) by mx1.freebsd.org (Postfix) with ESMTP id 2C3AF13C47E for ; Thu, 11 Oct 2007 17:40:57 +0000 (UTC) (envelope-from tching@arraynetworks.net) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Date: Thu, 11 Oct 2007 10:40:56 -0700 Message-ID: In-Reply-To: <470E5EED.404@elischer.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Supermicro H8DAE-2 support Thread-Index: AcgMLSncJNe7NUdPQ+Oz2LnliA17iAAAF4wg From: "Thomas Ching" To: "Julian Elischer" Cc: freebsd-smp@FreeBSD.org Subject: RE: Supermicro H8DAE-2 support X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 17:40:58 -0000 Hi, Julian: Thanks for your response. Our existing products (which heavily changed = the kernel code) were developed based on the 4.5 kernel that's why we = need to stick with it for a short while. Is there anything I can learn on the tricks you mentioned in your email? = I am open to examine all possibilities. Thanks Thomas -----Original Message----- From: Julian Elischer [mailto:julian@elischer.org]=20 Sent: Thursday, October 11, 2007 10:36 AM To: Thomas Ching Cc: freebsd-smp@FreeBSD.org Subject: Re: Supermicro H8DAE-2 support Thomas Ching wrote: > Hi, >=20 >=20 >=20 > I am a newbie to this so I apologize if I did not follow any protocol > that I am supposed to. >=20 >=20 >=20 > I am porting FreeBSD 4.5 to this board and I am just wondering if > anyone has any information that I can read. I am really concerned > about given how new the board is and 4.5 would probably not run on > it. >=20 Ok so explain why it needs to be 4.5? Assuming it does, you may be able to run it straight away or at worst with just a couple of tweeks, but there are tricks you may not know about to avoid running new = hardware on old systems. >=20 >=20 > It has to be 4.5 for legacy reasons. why? explain this in detail. >=20 >=20 >=20 > Thanks >=20 > Thomas >=20 >=20 > No virus found in this outgoing message. Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: > 10/11/2007 9:11 AM >=20 > _______________________________________________=20 > freebsd-smp@freebsd.org mailing list=20 > http://lists.freebsd.org/mailman/listinfo/freebsd-smp To unsubscribe, > send any mail to "freebsd-smp-unsubscribe@freebsd.org" No virus found in this incoming message. Checked by AVG Free Edition.=20 Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM =20 No virus found in this outgoing message. Checked by AVG Free Edition.=20 Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM =20 From owner-freebsd-smp@FreeBSD.ORG Thu Oct 11 17:46:21 2007 Return-Path: Delivered-To: freebsd-smp@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 797AD16A417 for ; Thu, 11 Oct 2007 17:46:21 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outN.internet-mail-service.net (outN.internet-mail-service.net [216.240.47.237]) by mx1.freebsd.org (Postfix) with ESMTP id 6DFE013C465 for ; Thu, 11 Oct 2007 17:46:21 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Thu, 11 Oct 2007 10:35:32 -0700 X-Client-Authorized: MaGic Cook1e 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 9D882126679; Thu, 11 Oct 2007 10:35:31 -0700 (PDT) Message-ID: <470E5EED.404@elischer.org> Date: Thu, 11 Oct 2007 10:35:41 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Thomas Ching References: In-Reply-To: Content-Type: text/plain; charset=windows-1250; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-smp@FreeBSD.org Subject: Re: Supermicro H8DAE-2 support X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 17:46:21 -0000 Thomas Ching wrote: > Hi, > > > > I am a newbie to this so I apologize if I did not follow any protocol > that I am supposed to. > > > > I am porting FreeBSD 4.5 to this board and I am just wondering if > anyone has any information that I can read. I am really concerned > about given how new the board is and 4.5 would probably not run on > it. > Ok so explain why it needs to be 4.5? Assuming it does, you may be able to run it straight away or at worst with just a couple of tweeks, but there are tricks you may not know about to avoid running new hardware on old systems. > > > It has to be 4.5 for legacy reasons. why? explain this in detail. > > > > Thanks > > Thomas > > > No virus found in this outgoing message. Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: > 10/11/2007 9:11 AM > > _______________________________________________ > freebsd-smp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-smp To unsubscribe, > send any mail to "freebsd-smp-unsubscribe@freebsd.org" From owner-freebsd-smp@FreeBSD.ORG Thu Oct 11 18:47:23 2007 Return-Path: Delivered-To: freebsd-smp@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5509F16A417 for ; Thu, 11 Oct 2007 18:47:23 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outE.internet-mail-service.net (outE.internet-mail-service.net [216.240.47.228]) by mx1.freebsd.org (Postfix) with ESMTP id 9390813C45A for ; Thu, 11 Oct 2007 18:47:22 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Thu, 11 Oct 2007 11:47:21 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 1D49412668D; Thu, 11 Oct 2007 11:47:21 -0700 (PDT) Message-ID: <470E6FC3.3080208@elischer.org> Date: Thu, 11 Oct 2007 11:47:31 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Thomas Ching References: In-Reply-To: Content-Type: text/plain; charset=windows-1250; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-smp@FreeBSD.org Subject: Re: Supermicro H8DAE-2 support X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 18:47:23 -0000 Thomas Ching wrote: > Hi, Julian: > > Thanks for your response. Our existing products (which heavily changed the kernel code) were developed based on the 4.5 kernel that's why we need to stick with it for a short while. > > Is there anything I can learn on the tricks you mentioned in your email? I am open to examine all possibilities. > > Thanks > Thomas > > -----Original Message----- > From: Julian Elischer [mailto:julian@elischer.org] > Sent: Thursday, October 11, 2007 10:36 AM > To: Thomas Ching > Cc: freebsd-smp@FreeBSD.org > Subject: Re: Supermicro H8DAE-2 support > > Thomas Ching wrote: >> Hi, >> >> >> >> I am a newbie to this so I apologize if I did not follow any protocol >> that I am supposed to. >> >> >> >> I am porting FreeBSD 4.5 to this board and I am just wondering if >> anyone has any information that I can read. I am really concerned >> about given how new the board is and 4.5 would probably not run on >> it. >> > > Ok so explain why it needs to be 4.5? > > Assuming it does, you may be able to run it straight away > or at worst with just a couple of tweeks, > but there are tricks you may not know about to avoid running new hardware > on old systems. > >> >> It has to be 4.5 for legacy reasons. > > why? > > explain this in detail. It's a pitty you have kernel changes because if you had just userland requirements, I'd run a 6.2 system and make a 4.5 jail to match the apps. Since you have kernel changes that won't work. however I'd still suggest moving up to at least 4.11. The changes between 4.5 and 4.11 were not that great, but a lot of newer hardware was supported. Your kernel changes will nearly all apply with minimal change (if any at all), but you may have a chance to get some newer hardware working easier. There are also security and bug fixes.. in fact I'd go for a RELENG_4 system (i.e. from the 4 branch but after 4.11.. you compile it yourself). what KIND of changes? (some changes can be ported forward to 5.x really easy too. It depends on what kind they are and where they are. > >> >> >> Thanks >> >> Thomas >> >> >> No virus found in this outgoing message. Checked by AVG Free Edition. >> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: >> 10/11/2007 9:11 AM >> >> _______________________________________________ >> freebsd-smp@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-smp To unsubscribe, >> send any mail to "freebsd-smp-unsubscribe@freebsd.org" > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM > From owner-freebsd-smp@FreeBSD.ORG Thu Oct 11 21:01:54 2007 Return-Path: Delivered-To: freebsd-smp@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A60B516A417 for ; Thu, 11 Oct 2007 21:01:54 +0000 (UTC) (envelope-from tching@arraynetworks.net) Received: from Exchange.arraynetworks.net (mail.arraynetworks.net [12.22.49.71]) by mx1.freebsd.org (Postfix) with ESMTP id 81ADC13C459 for ; Thu, 11 Oct 2007 21:01:54 +0000 (UTC) (envelope-from tching@arraynetworks.net) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Date: Thu, 11 Oct 2007 14:01:52 -0700 Message-ID: In-Reply-To: <470E6FC3.3080208@elischer.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Supermicro H8DAE-2 support Thread-Index: AcgMNy88Ezx+w7U4THSJ3bS6lZnBhAAEl2qg From: "Thomas Ching" To: "Julian Elischer" Cc: freebsd-smp@FreeBSD.org Subject: RE: Supermicro H8DAE-2 support X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 21:01:54 -0000 Hi, Julian: Thanks for the useful info; I think I will start with Vanilla 4.5 on the = board first to see if it's even possible. If no luck, I will try 4.11.=20 Regarding the changes, I am actually new to the company and I do not = know all the history and details, all I am told is "massive". I think mostly are on the TCP stack. I will learn more about it in the = next few weeks. Again appreciate your fast responses and ideas/suggestions. Thomas -----Original Message----- From: Julian Elischer [mailto:julian@elischer.org]=20 Sent: Thursday, October 11, 2007 11:48 AM To: Thomas Ching Cc: freebsd-smp@FreeBSD.org Subject: Re: Supermicro H8DAE-2 support Thomas Ching wrote: > Hi, Julian: >=20 > Thanks for your response. Our existing products (which heavily changed = the kernel code) were developed based on the 4.5 kernel that's why we = need to stick with it for a short while. >=20 > Is there anything I can learn on the tricks you mentioned in your = email? I am open to examine all possibilities. >=20 > Thanks > Thomas >=20 > -----Original Message----- > From: Julian Elischer [mailto:julian@elischer.org]=20 > Sent: Thursday, October 11, 2007 10:36 AM > To: Thomas Ching > Cc: freebsd-smp@FreeBSD.org > Subject: Re: Supermicro H8DAE-2 support >=20 > Thomas Ching wrote: >> Hi, >> >> >> >> I am a newbie to this so I apologize if I did not follow any protocol >> that I am supposed to. >> >> >> >> I am porting FreeBSD 4.5 to this board and I am just wondering if >> anyone has any information that I can read. I am really concerned >> about given how new the board is and 4.5 would probably not run on >> it. >> >=20 > Ok so explain why it needs to be 4.5? >=20 > Assuming it does, you may be able to run it straight away > or at worst with just a couple of tweeks, > but there are tricks you may not know about to avoid running new = hardware > on old systems. >=20 >> >> It has to be 4.5 for legacy reasons. >=20 > why? >=20 > explain this in detail. It's a pitty you have kernel changes because if you had just userland = requirements, I'd run a 6.2 system and make a 4.5 jail to match the apps. Since you have kernel changes that won't work. however I'd still suggest = moving up to at least 4.11. The changes between 4.5 and 4.11 were not that great, but a lot of newer = hardware was supported. Your kernel changes will nearly all apply with minimal = change=20 (if any at all), but you may have a chance to get some newer hardware = working easier. There are also security and bug fixes.. in fact I'd go for a RELENG_4 system (i.e. from the 4 branch but after 4.11.. you compile it = yourself). what KIND of changes? (some changes can be ported forward to 5.x really = easy too. It depends on what kind they are and where they are. >=20 >> >> >> Thanks >> >> Thomas >> >> >> No virus found in this outgoing message. Checked by AVG Free Edition. >> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: >> 10/11/2007 9:11 AM >> >> _______________________________________________=20 >> freebsd-smp@freebsd.org mailing list=20 >> http://lists.freebsd.org/mailman/listinfo/freebsd-smp To unsubscribe, >> send any mail to "freebsd-smp-unsubscribe@freebsd.org" >=20 >=20 > No virus found in this incoming message. > Checked by AVG Free Edition.=20 > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM > =20 >=20 > No virus found in this outgoing message. > Checked by AVG Free Edition.=20 > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM > =20 No virus found in this incoming message. Checked by AVG Free Edition.=20 Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM =20 No virus found in this outgoing message. Checked by AVG Free Edition.=20 Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM =20 From owner-freebsd-smp@FreeBSD.ORG Thu Oct 11 21:19:14 2007 Return-Path: Delivered-To: freebsd-smp@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA99316A417 for ; Thu, 11 Oct 2007 21:19:14 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outX.internet-mail-service.net (outX.internet-mail-service.net [216.240.47.247]) by mx1.freebsd.org (Postfix) with ESMTP id 8EAB013C457 for ; Thu, 11 Oct 2007 21:19:14 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Thu, 11 Oct 2007 14:19:13 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 5DF75126686; Thu, 11 Oct 2007 14:19:13 -0700 (PDT) Message-ID: <470E9357.1080905@elischer.org> Date: Thu, 11 Oct 2007 14:19:19 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Thomas Ching References: In-Reply-To: Content-Type: text/plain; charset=windows-1250; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-smp@FreeBSD.org Subject: Re: Supermicro H8DAE-2 support X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 21:19:14 -0000 Thomas Ching wrote: > Hi, Julian: > > Thanks for the useful info; I think I will start with Vanilla 4.5 on the board first to see if it's even possible. If no luck, I will try 4.11. > > Regarding the changes, I am actually new to the company and I do not know all the history and details, all I am told is "massive". > > I think mostly are on the TCP stack. I will learn more about it in the next few weeks. "Massive" is relative. 4.x doesn't support using > 1 CPU in the kernel at one time. So unless this is what your changes do, it means you can't use your 2nd CPU for networking.. anyhow, good luck and do come back if you have problems. > > Again appreciate your fast responses and ideas/suggestions. > > Thomas > > -----Original Message----- > From: Julian Elischer [mailto:julian@elischer.org] > Sent: Thursday, October 11, 2007 11:48 AM > To: Thomas Ching > Cc: freebsd-smp@FreeBSD.org > Subject: Re: Supermicro H8DAE-2 support > > Thomas Ching wrote: >> Hi, Julian: >> >> Thanks for your response. Our existing products (which heavily changed the kernel code) were developed based on the 4.5 kernel that's why we need to stick with it for a short while. >> >> Is there anything I can learn on the tricks you mentioned in your email? I am open to examine all possibilities. >> >> Thanks >> Thomas >> >> -----Original Message----- >> From: Julian Elischer [mailto:julian@elischer.org] >> Sent: Thursday, October 11, 2007 10:36 AM >> To: Thomas Ching >> Cc: freebsd-smp@FreeBSD.org >> Subject: Re: Supermicro H8DAE-2 support >> >> Thomas Ching wrote: >>> Hi, >>> >>> >>> >>> I am a newbie to this so I apologize if I did not follow any protocol >>> that I am supposed to. >>> >>> >>> >>> I am porting FreeBSD 4.5 to this board and I am just wondering if >>> anyone has any information that I can read. I am really concerned >>> about given how new the board is and 4.5 would probably not run on >>> it. >>> >> Ok so explain why it needs to be 4.5? >> >> Assuming it does, you may be able to run it straight away >> or at worst with just a couple of tweeks, >> but there are tricks you may not know about to avoid running new hardware >> on old systems. >> >>> It has to be 4.5 for legacy reasons. >> why? >> >> explain this in detail. > > It's a pitty you have kernel changes because if you had just userland requirements, > I'd run a 6.2 system and make a 4.5 jail to match the apps. > > Since you have kernel changes that won't work. however I'd still suggest > moving up to at least 4.11. > The changes between 4.5 and 4.11 were not that great, but a lot of newer hardware > was supported. Your kernel changes will nearly all apply with minimal change > (if any at all), but you may have a chance to get some newer hardware working easier. > There are also security and bug fixes.. in fact I'd go for a RELENG_4 > system (i.e. from the 4 branch but after 4.11.. you compile it yourself). > > what KIND of changes? (some changes can be ported forward to 5.x really easy too. > It depends on what kind they are and where they are. > > > > > > >>> >>> Thanks >>> >>> Thomas >>> >>> >>> No virus found in this outgoing message. Checked by AVG Free Edition. >>> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: >>> 10/11/2007 9:11 AM >>> >>> _______________________________________________ >>> freebsd-smp@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-smp To unsubscribe, >>> send any mail to "freebsd-smp-unsubscribe@freebsd.org" >> >> No virus found in this incoming message. >> Checked by AVG Free Edition. >> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM >> >> >> No virus found in this outgoing message. >> Checked by AVG Free Edition. >> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM >> > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM > From owner-freebsd-smp@FreeBSD.ORG Thu Oct 11 21:30:21 2007 Return-Path: Delivered-To: freebsd-smp@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2043B16A418 for ; Thu, 11 Oct 2007 21:30:21 +0000 (UTC) (envelope-from tching@arraynetworks.net) Received: from Exchange.arraynetworks.net (mail.arraynetworks.net [12.22.49.71]) by mx1.freebsd.org (Postfix) with ESMTP id EDF0F13C467 for ; Thu, 11 Oct 2007 21:30:20 +0000 (UTC) (envelope-from tching@arraynetworks.net) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Date: Thu, 11 Oct 2007 14:30:19 -0700 Message-ID: In-Reply-To: <470E9357.1080905@elischer.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Supermicro H8DAE-2 support Thread-Index: AcgMTGcKeHsEOJDCQdy2uSeDo5bU0QAATsow From: "Thomas Ching" To: "Julian Elischer" Cc: freebsd-smp@FreeBSD.org Subject: RE: Supermicro H8DAE-2 support X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 21:30:21 -0000 Thanks, it's very interesting regarding your mention of SMP support = (again I am new to this so I don't know the history that well). According to 4.5 release notes, it does: = http://www.freebsd.org/releases/4.5R/hardware-i386.html In either case, we do not intend to run on muti cores until we migrate = to 6.2 so it's not a problem for now. Thomas -----Original Message----- From: Julian Elischer [mailto:julian@elischer.org]=20 Sent: Thursday, October 11, 2007 2:19 PM To: Thomas Ching Cc: freebsd-smp@FreeBSD.org Subject: Re: Supermicro H8DAE-2 support Thomas Ching wrote: > Hi, Julian: >=20 > Thanks for the useful info; I think I will start with Vanilla 4.5 on = the board first to see if it's even possible. If no luck, I will try = 4.11.=20 >=20 > Regarding the changes, I am actually new to the company and I do not = know all the history and details, all I am told is "massive". >=20 > I think mostly are on the TCP stack. I will learn more about it in the = next few weeks. "Massive" is relative. 4.x doesn't support using > 1 CPU in the kernel at one time. So unless this is what your changes do, it means you can't use your 2nd = CPU for networking.. anyhow, good luck and do come back if you have problems. >=20 > Again appreciate your fast responses and ideas/suggestions. >=20 > Thomas >=20 > -----Original Message----- > From: Julian Elischer [mailto:julian@elischer.org]=20 > Sent: Thursday, October 11, 2007 11:48 AM > To: Thomas Ching > Cc: freebsd-smp@FreeBSD.org > Subject: Re: Supermicro H8DAE-2 support >=20 > Thomas Ching wrote: >> Hi, Julian: >> >> Thanks for your response. Our existing products (which heavily = changed the kernel code) were developed based on the 4.5 kernel that's = why we need to stick with it for a short while. >> >> Is there anything I can learn on the tricks you mentioned in your = email? I am open to examine all possibilities. >> >> Thanks >> Thomas >> >> -----Original Message----- >> From: Julian Elischer [mailto:julian@elischer.org]=20 >> Sent: Thursday, October 11, 2007 10:36 AM >> To: Thomas Ching >> Cc: freebsd-smp@FreeBSD.org >> Subject: Re: Supermicro H8DAE-2 support >> >> Thomas Ching wrote: >>> Hi, >>> >>> >>> >>> I am a newbie to this so I apologize if I did not follow any = protocol >>> that I am supposed to. >>> >>> >>> >>> I am porting FreeBSD 4.5 to this board and I am just wondering if >>> anyone has any information that I can read. I am really concerned >>> about given how new the board is and 4.5 would probably not run on >>> it. >>> >> Ok so explain why it needs to be 4.5? >> >> Assuming it does, you may be able to run it straight away >> or at worst with just a couple of tweeks, >> but there are tricks you may not know about to avoid running new = hardware >> on old systems. >> >>> It has to be 4.5 for legacy reasons. >> why? >> >> explain this in detail. >=20 > It's a pitty you have kernel changes because if you had just userland = requirements, > I'd run a 6.2 system and make a 4.5 jail to match the apps. >=20 > Since you have kernel changes that won't work. however I'd still = suggest=20 > moving up to at least 4.11. > The changes between 4.5 and 4.11 were not that great, but a lot of = newer hardware > was supported. Your kernel changes will nearly all apply with minimal = change=20 > (if any at all), but you may have a chance to get some newer hardware = working easier. > There are also security and bug fixes.. in fact I'd go for a RELENG_4 > system (i.e. from the 4 branch but after 4.11.. you compile it = yourself). >=20 > what KIND of changes? (some changes can be ported forward to 5.x = really easy too. > It depends on what kind they are and where they are. >=20 >=20 >=20 >=20 >=20 >=20 >>> >>> Thanks >>> >>> Thomas >>> >>> >>> No virus found in this outgoing message. Checked by AVG Free = Edition. >>> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: >>> 10/11/2007 9:11 AM >>> >>> _______________________________________________=20 >>> freebsd-smp@freebsd.org mailing list=20 >>> http://lists.freebsd.org/mailman/listinfo/freebsd-smp To = unsubscribe, >>> send any mail to "freebsd-smp-unsubscribe@freebsd.org" >> >> No virus found in this incoming message. >> Checked by AVG Free Edition.=20 >> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM >> =20 >> >> No virus found in this outgoing message. >> Checked by AVG Free Edition.=20 >> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM >> =20 >=20 >=20 > No virus found in this incoming message. > Checked by AVG Free Edition.=20 > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM > =20 >=20 > No virus found in this outgoing message. > Checked by AVG Free Edition.=20 > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM > =20 No virus found in this incoming message. Checked by AVG Free Edition.=20 Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM =20 No virus found in this outgoing message. Checked by AVG Free Edition.=20 Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM =20 From owner-freebsd-smp@FreeBSD.ORG Thu Oct 11 21:37:49 2007 Return-Path: Delivered-To: freebsd-smp@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F29716A41B for ; Thu, 11 Oct 2007 21:37:49 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (unknown [IPv6:2001:5c0:8fff:fffe::214d]) by mx1.freebsd.org (Postfix) with ESMTP id C625813C474 for ; Thu, 11 Oct 2007 21:37:48 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1Ig5ic-000MM9-OJ; Thu, 11 Oct 2007 17:37:22 -0400 Date: Thu, 11 Oct 2007 17:37:22 -0400 From: Gary Palmer To: Thomas Ching Message-ID: <20071011213722.GA54662@in-addr.com> Mail-Followup-To: Thomas Ching , Julian Elischer , freebsd-smp@FreeBSD.org References: <470E9357.1080905@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Cc: freebsd-smp@FreeBSD.org, Julian Elischer Subject: Re: Supermicro H8DAE-2 support X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 21:37:49 -0000 On Thu, Oct 11, 2007 at 02:30:19PM -0700, Thomas Ching wrote: > Thanks, it's very interesting regarding your mention of SMP support (again I am new to this so I don't know the history that well). > > According to 4.5 release notes, it does: http://www.freebsd.org/releases/4.5R/hardware-i386.html Although the 3.x and 4.x branches of FreeBSD support multi-CPU operation, they only supported running multiple processes in user space at the same time. You could not have multiple CPUs in the kernel at the same time due to the "Giant" lock that serialised access to the kernel. > In either case, we do not intend to run on muti cores until we migrate to 6.2 so it's not a problem for now. > > Thomas > > -----Original Message----- > From: Julian Elischer [mailto:julian@elischer.org] > Sent: Thursday, October 11, 2007 2:19 PM > To: Thomas Ching > Cc: freebsd-smp@FreeBSD.org > Subject: Re: Supermicro H8DAE-2 support > > Thomas Ching wrote: > > Hi, Julian: > > > > Thanks for the useful info; I think I will start with Vanilla 4.5 on the board first to see if it's even possible. If no luck, I will try 4.11. > > > > Regarding the changes, I am actually new to the company and I do not know all the history and details, all I am told is "massive". > > > > I think mostly are on the TCP stack. I will learn more about it in the next few weeks. > > "Massive" is relative. > 4.x doesn't support using > 1 CPU in the kernel at one time. > So unless this is what your changes do, it means you can't use your 2nd CPU for networking.. > > anyhow, good luck and do come back if you have problems. > > > > > Again appreciate your fast responses and ideas/suggestions. > > > > Thomas > > > > -----Original Message----- > > From: Julian Elischer [mailto:julian@elischer.org] > > Sent: Thursday, October 11, 2007 11:48 AM > > To: Thomas Ching > > Cc: freebsd-smp@FreeBSD.org > > Subject: Re: Supermicro H8DAE-2 support > > > > Thomas Ching wrote: > >> Hi, Julian: > >> > >> Thanks for your response. Our existing products (which heavily changed the kernel code) were developed based on the 4.5 kernel that's why we need to stick with it for a short while. > >> > >> Is there anything I can learn on the tricks you mentioned in your email? I am open to examine all possibilities. > >> > >> Thanks > >> Thomas > >> > >> -----Original Message----- > >> From: Julian Elischer [mailto:julian@elischer.org] > >> Sent: Thursday, October 11, 2007 10:36 AM > >> To: Thomas Ching > >> Cc: freebsd-smp@FreeBSD.org > >> Subject: Re: Supermicro H8DAE-2 support > >> > >> Thomas Ching wrote: > >>> Hi, > >>> > >>> > >>> > >>> I am a newbie to this so I apologize if I did not follow any protocol > >>> that I am supposed to. > >>> > >>> > >>> > >>> I am porting FreeBSD 4.5 to this board and I am just wondering if > >>> anyone has any information that I can read. I am really concerned > >>> about given how new the board is and 4.5 would probably not run on > >>> it. > >>> > >> Ok so explain why it needs to be 4.5? > >> > >> Assuming it does, you may be able to run it straight away > >> or at worst with just a couple of tweeks, > >> but there are tricks you may not know about to avoid running new hardware > >> on old systems. > >> > >>> It has to be 4.5 for legacy reasons. > >> why? > >> > >> explain this in detail. > > > > It's a pitty you have kernel changes because if you had just userland requirements, > > I'd run a 6.2 system and make a 4.5 jail to match the apps. > > > > Since you have kernel changes that won't work. however I'd still suggest > > moving up to at least 4.11. > > The changes between 4.5 and 4.11 were not that great, but a lot of newer hardware > > was supported. Your kernel changes will nearly all apply with minimal change > > (if any at all), but you may have a chance to get some newer hardware working easier. > > There are also security and bug fixes.. in fact I'd go for a RELENG_4 > > system (i.e. from the 4 branch but after 4.11.. you compile it yourself). > > > > what KIND of changes? (some changes can be ported forward to 5.x really easy too. > > It depends on what kind they are and where they are. > > > > > > > > > > > > > >>> > >>> Thanks > >>> > >>> Thomas > >>> > >>> > >>> No virus found in this outgoing message. Checked by AVG Free Edition. > >>> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: > >>> 10/11/2007 9:11 AM > >>> > >>> _______________________________________________ > >>> freebsd-smp@freebsd.org mailing list > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-smp To unsubscribe, > >>> send any mail to "freebsd-smp-unsubscribe@freebsd.org" > >> > >> No virus found in this incoming message. > >> Checked by AVG Free Edition. > >> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM > >> > >> > >> No virus found in this outgoing message. > >> Checked by AVG Free Edition. > >> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM > >> > > > > > > No virus found in this incoming message. > > Checked by AVG Free Edition. > > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM > > > > > > No virus found in this outgoing message. > > Checked by AVG Free Edition. > > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM > > > > > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: 10/11/2007 9:11 AM > > _______________________________________________ > freebsd-smp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-smp > To unsubscribe, send any mail to "freebsd-smp-unsubscribe@freebsd.org" > > From owner-freebsd-smp@FreeBSD.ORG Thu Oct 11 21:40:26 2007 Return-Path: Delivered-To: freebsd-smp@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46EB716A418 for ; Thu, 11 Oct 2007 21:40:26 +0000 (UTC) (envelope-from tching@arraynetworks.net) Received: from Exchange.arraynetworks.net (mail.arraynetworks.net [12.22.49.71]) by mx1.freebsd.org (Postfix) with ESMTP id 1E93013C45A for ; Thu, 11 Oct 2007 21:40:26 +0000 (UTC) (envelope-from tching@arraynetworks.net) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Date: Thu, 11 Oct 2007 14:40:25 -0700 Message-ID: In-Reply-To: <20071011213722.GA54662@in-addr.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Supermicro H8DAE-2 support Thread-Index: AcgMTv/3e94qVbR4SGOmktOFqx0mJwAAE67A From: "Thomas Ching" To: "Gary Palmer" Cc: freebsd-smp@FreeBSD.org, Julian Elischer Subject: RE: Supermicro H8DAE-2 support X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2007 21:40:26 -0000 That's very helpful, thanks. Thomas -----Original Message----- From: Gary Palmer [mailto:gpalmer@freebsd.org]=20 Sent: Thursday, October 11, 2007 2:37 PM To: Thomas Ching Cc: Julian Elischer; freebsd-smp@FreeBSD.org Subject: Re: Supermicro H8DAE-2 support On Thu, Oct 11, 2007 at 02:30:19PM -0700, Thomas Ching wrote: > Thanks, it's very interesting regarding your mention of SMP support = (again I am new to this so I don't know the history that well). >=20 > According to 4.5 release notes, it does: = http://www.freebsd.org/releases/4.5R/hardware-i386.html Although the 3.x and 4.x branches of FreeBSD support multi-CPU = operation, they only supported running multiple processes in user space at the same time. You could not have multiple CPUs in the kernel at the same time due to the "Giant" lock that serialised access to the kernel. > In either case, we do not intend to run on muti cores until we migrate = to 6.2 so it's not a problem for now. >=20 > Thomas >=20 > -----Original Message----- > From: Julian Elischer [mailto:julian@elischer.org]=20 > Sent: Thursday, October 11, 2007 2:19 PM > To: Thomas Ching > Cc: freebsd-smp@FreeBSD.org > Subject: Re: Supermicro H8DAE-2 support >=20 > Thomas Ching wrote: > > Hi, Julian: > >=20 > > Thanks for the useful info; I think I will start with Vanilla 4.5 on = the board first to see if it's even possible. If no luck, I will try = 4.11.=20 > >=20 > > Regarding the changes, I am actually new to the company and I do not = know all the history and details, all I am told is "massive". > >=20 > > I think mostly are on the TCP stack. I will learn more about it in = the next few weeks. >=20 > "Massive" is relative. > 4.x doesn't support using > 1 CPU in the kernel at one time. > So unless this is what your changes do, it means you can't use your = 2nd CPU for networking.. >=20 > anyhow, good luck and do come back if you have problems. >=20 > >=20 > > Again appreciate your fast responses and ideas/suggestions. > >=20 > > Thomas > >=20 > > -----Original Message----- > > From: Julian Elischer [mailto:julian@elischer.org]=20 > > Sent: Thursday, October 11, 2007 11:48 AM > > To: Thomas Ching > > Cc: freebsd-smp@FreeBSD.org > > Subject: Re: Supermicro H8DAE-2 support > >=20 > > Thomas Ching wrote: > >> Hi, Julian: > >> > >> Thanks for your response. Our existing products (which heavily = changed the kernel code) were developed based on the 4.5 kernel that's = why we need to stick with it for a short while. > >> > >> Is there anything I can learn on the tricks you mentioned in your = email? I am open to examine all possibilities. > >> > >> Thanks > >> Thomas > >> > >> -----Original Message----- > >> From: Julian Elischer [mailto:julian@elischer.org]=20 > >> Sent: Thursday, October 11, 2007 10:36 AM > >> To: Thomas Ching > >> Cc: freebsd-smp@FreeBSD.org > >> Subject: Re: Supermicro H8DAE-2 support > >> > >> Thomas Ching wrote: > >>> Hi, > >>> > >>> > >>> > >>> I am a newbie to this so I apologize if I did not follow any = protocol > >>> that I am supposed to. > >>> > >>> > >>> > >>> I am porting FreeBSD 4.5 to this board and I am just wondering if > >>> anyone has any information that I can read. I am really concerned > >>> about given how new the board is and 4.5 would probably not run on > >>> it. > >>> > >> Ok so explain why it needs to be 4.5? > >> > >> Assuming it does, you may be able to run it straight away > >> or at worst with just a couple of tweeks, > >> but there are tricks you may not know about to avoid running new = hardware > >> on old systems. > >> > >>> It has to be 4.5 for legacy reasons. > >> why? > >> > >> explain this in detail. > >=20 > > It's a pitty you have kernel changes because if you had just = userland requirements, > > I'd run a 6.2 system and make a 4.5 jail to match the apps. > >=20 > > Since you have kernel changes that won't work. however I'd still = suggest=20 > > moving up to at least 4.11. > > The changes between 4.5 and 4.11 were not that great, but a lot of = newer hardware > > was supported. Your kernel changes will nearly all apply with = minimal change=20 > > (if any at all), but you may have a chance to get some newer = hardware working easier. > > There are also security and bug fixes.. in fact I'd go for a = RELENG_4 > > system (i.e. from the 4 branch but after 4.11.. you compile it = yourself). > >=20 > > what KIND of changes? (some changes can be ported forward to 5.x = really easy too. > > It depends on what kind they are and where they are. > >=20 > >=20 > >=20 > >=20 > >=20 > >=20 > >>> > >>> Thanks > >>> > >>> Thomas > >>> > >>> > >>> No virus found in this outgoing message. Checked by AVG Free = Edition. > >>> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: > >>> 10/11/2007 9:11 AM > >>> > >>> _______________________________________________=20 > >>> freebsd-smp@freebsd.org mailing list=20 > >>> http://lists.freebsd.org/mailman/listinfo/freebsd-smp To = unsubscribe, > >>> send any mail to "freebsd-smp-unsubscribe@freebsd.org" > >> > >> No virus found in this incoming message. > >> Checked by AVG Free Edition.=20 > >> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM > >> =20 > >> > >> No virus found in this outgoing message. > >> Checked by AVG Free Edition.=20 > >> Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM > >> =20 > >=20 > >=20 > > No virus found in this incoming message. > > Checked by AVG Free Edition.=20 > > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM > > =20 > >=20 > > No virus found in this outgoing message. > > Checked by AVG Free Edition.=20 > > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM > > =20 >=20 >=20 > No virus found in this incoming message. > Checked by AVG Free Edition.=20 > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM > =20 >=20 > No virus found in this outgoing message. > Checked by AVG Free Edition.=20 > Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM > =20 > _______________________________________________ > freebsd-smp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-smp > To unsubscribe, send any mail to "freebsd-smp-unsubscribe@freebsd.org" >=20 >=20 No virus found in this incoming message. Checked by AVG Free Edition.=20 Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM =20 No virus found in this outgoing message. Checked by AVG Free Edition.=20 Version: 7.5.488 / Virus Database: 269.14.8/1063 - Release Date: = 10/11/2007 9:11 AM =20 From owner-freebsd-smp@FreeBSD.ORG Fri Oct 12 02:28:00 2007 Return-Path: Delivered-To: freebsd-smp@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63E6116A41B for ; Fri, 12 Oct 2007 02:28:00 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outQ.internet-mail-service.net (outQ.internet-mail-service.net [216.240.47.240]) by mx1.freebsd.org (Postfix) with ESMTP id 31D7B13C455 for ; Fri, 12 Oct 2007 02:28:00 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Thu, 11 Oct 2007 19:27:59 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id A4DBD1266A3; Thu, 11 Oct 2007 19:27:58 -0700 (PDT) Message-ID: <470EDBB9.1010005@elischer.org> Date: Thu, 11 Oct 2007 19:28:09 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Thomas Ching References: In-Reply-To: Content-Type: text/plain; charset=windows-1250; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-smp@FreeBSD.org Subject: Re: Supermicro H8DAE-2 support X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2007 02:28:00 -0000 Thomas Ching wrote: > Thanks, it's very interesting regarding your mention of SMP support (again I am new to this so I don't know the history that well). > > According to 4.5 release notes, it does: http://www.freebsd.org/releases/4.5R/hardware-i386.html not while in the kernel.. it's "one at a time". > > In either case, we do not intend to run on muti cores until we migrate to 6.2 so it's not a problem for now. > > Thomas > From owner-freebsd-smp@FreeBSD.ORG Fri Oct 12 20:22:49 2007 Return-Path: Delivered-To: smp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D49A16A418; Fri, 12 Oct 2007 20:22:49 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 44B1B13C46B; Fri, 12 Oct 2007 20:22:49 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 486A71A4D8B; Fri, 12 Oct 2007 13:00:06 -0700 (PDT) Date: Fri, 12 Oct 2007 13:00:06 -0700 From: Alfred Perlstein To: smp@freebsd.org Message-ID: <20071012200006.GK31826@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: jkoshy@freebsd.org Subject: hwpmc dealing with sparse cpu systems. X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2007 20:22:49 -0000 One of the engineers here seems to have found a bug in the hwpmc_mod.c module. The problem we have is that cpuids can be greater than mp_ncpus due to sparseness. Does the fix here make sense? (replace mp_ncpus with MAXCPU) I would like to commit it. -Alfred ----- Forwarded message from Alfred Perlstein ----- From: "Sunil Mudunuri" Subject: Re: hwpmc on mpsdk. Date: Thu, 11 Oct 2007 18:11:27 -0700 Message-ID: <470EC9BF.5070607@juniper.net> User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) Looking at the code in hwpmc_mod.c, I feel that the mp_ncpus (global) is wrongly used in this module. While mp_ncpus is the count of active cpus in the system, this is being used to range check a cpu id(active/inactive) which can be greater than mp_ncpus. The code works fine in systems which has all the cpu's active eg. SPU(australia), but is causing crashes in mpsdk where we have the active cpus interleaved with idle cpu's. I replaced mp_ncpus with MAXCPU in almost all the places and it works fine. So this should be fixed in the FreeBSD proper, I guess. Alfred/Girish, can you push this to be fixed in FreeBSD Thanks, Sunil ----- End forwarded message ----- -- - Alfred Perlstein From owner-freebsd-smp@FreeBSD.ORG Fri Oct 12 20:38:15 2007 Return-Path: Delivered-To: smp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3C9A16A41B; Fri, 12 Oct 2007 20:38:15 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id E68A813C467; Fri, 12 Oct 2007 20:38:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 214179135-1834499 for multiple; Fri, 12 Oct 2007 16:36:24 -0400 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l9CKc8Kf042183; Fri, 12 Oct 2007 16:38:11 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: Alfred Perlstein Date: Fri, 12 Oct 2007 16:23:38 -0400 User-Agent: KMail/1.9.6 References: <20071012200006.GK31826@elvis.mu.org> In-Reply-To: <20071012200006.GK31826@elvis.mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710121623.38782.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Fri, 12 Oct 2007 16:38:11 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/4533/Fri Oct 12 06:59:29 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: jkoshy@freebsd.org, smp@freebsd.org Subject: Re: hwpmc dealing with sparse cpu systems. X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2007 20:38:15 -0000 On Friday 12 October 2007 04:00:06 pm Alfred Perlstein wrote: > One of the engineers here seems to have found a bug in the > hwpmc_mod.c module. The problem we have is that cpuids can > be greater than mp_ncpus due to sparseness. > > Does the fix here make sense? (replace mp_ncpus with MAXCPU) > > I would like to commit it. Actually, mp_maxid is what you should use. It is guaranteed that all CPU IDs are <= mp_maxid. > -Alfred > > ----- Forwarded message from Alfred Perlstein ----- > > From: "Sunil Mudunuri" > Subject: Re: hwpmc on mpsdk. > Date: Thu, 11 Oct 2007 18:11:27 -0700 > Message-ID: <470EC9BF.5070607@juniper.net> > User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) > > Looking at the code in hwpmc_mod.c, I feel that > the mp_ncpus (global) is wrongly used in this module. > > While mp_ncpus is the count of active cpus in the system, > this is being used to range check a cpu id(active/inactive) which can be > greater than mp_ncpus. > > The code works fine in systems which has all the cpu's active eg. > SPU(australia), but is causing crashes > in mpsdk where we have the active cpus interleaved with idle cpu's. > > I replaced mp_ncpus with MAXCPU in almost all the places and it works fine. > > So this should be fixed in the FreeBSD proper, I guess. > > Alfred/Girish, can you push this to be fixed in FreeBSD > > Thanks, > Sunil > > > > ----- End forwarded message ----- > > -- > - Alfred Perlstein > -- John Baldwin From owner-freebsd-smp@FreeBSD.ORG Sat Oct 13 06:12:02 2007 Return-Path: Delivered-To: smp@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0475616A41B for ; Sat, 13 Oct 2007 06:12:02 +0000 (UTC) (envelope-from jkoshy.freebsd@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id DF4FC13C465 for ; Sat, 13 Oct 2007 06:12:01 +0000 (UTC) (envelope-from jkoshy.freebsd@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1273139waf for ; Fri, 12 Oct 2007 23:12:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:date:message-id:to:cc:subject:in-reply-to:references:user-agent:mime-version:content-type:from:sender; bh=Qc4E7/Nv698jbF2iA+sf1YPyFDoBvJgB1Ekcc4bVGb4=; b=SesNgOqBpd0Pf53qzcyLCgzvQAy1nuMjuOJgneahxSpaWy3P6tpgcpsnnurKr5uUUOmOWE5KpQFA/JsI30oGsY4Ai+yRr8bXfHpSOIoeGEidFN55O7Jh8ie28webxXBGO3YGo72EVtgZSKz3+T+oRTBCux7dJZY/OAbE6CF+N7U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:message-id:to:cc:subject:in-reply-to:references:user-agent:mime-version:content-type:from:sender; b=gaWbZIwhcUL+jON/Yaz3WaP0YZ1In7cLcAlmFllgBnAhb9OCgMY0aorSSf2D7bTiqzAPyWHmMo/DJ0m0obrroBeYMeV+/QBQLuS5O/nTF3xLFmml64zrYtwnEuh5zQmgAED3haCMf+5VLkfQGNJl+qc8qf4wRtyoSWrhnIZJCkk= Received: by 10.114.53.1 with SMTP id b1mr4382388waa.1192254242763; Fri, 12 Oct 2007 22:44:02 -0700 (PDT) Received: from moria.unixconsulting.co.in ( [59.88.120.188]) by mx.google.com with ESMTPS id k21sm1979720waf.2007.10.12.22.43.54 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 12 Oct 2007 22:44:02 -0700 (PDT) Date: Sat, 13 Oct 2007 09:37:15 +0530 Message-ID: <86k5prac98.wl%koshy@unixconsulting.co.in> To: Alfred Perlstein In-Reply-To: <20071012200006.GK31826@elvis.mu.org> References: <20071012200006.GK31826@elvis.mu.org> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/21.3 (amd64--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII From: Joseph Koshy Sender: Joseph Koshy Cc: jkoshy@freebsd.org, smp@freebsd.org Subject: Re: hwpmc dealing with sparse cpu systems. X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Oct 2007 06:12:02 -0000 > One of the engineers here seems to have found a bug in the > hwpmc_mod.c module. The problem we have is that cpuids can be > greater than mp_ncpus due to sparseness. > Does the fix here make sense? (replace mp_ncpus with MAXCPU) No, a simple global substitution would probably be incorrect because it would allow userland to get hwpmc to attempt operations on non-existent CPUs. I will look into this. Regards, Koshy