From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1Dxj4t-0004BI-7K for garchives@archives.gentoo.org; Wed, 27 Jul 2005 10:23:55 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6RAKBaq022100; Wed, 27 Jul 2005 10:20:11 GMT Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j6RAKBne018928 for ; Wed, 27 Jul 2005 10:20:11 GMT Received: from root by ciao.gmane.org with local (Exim 4.43) id 1Dxj18-0005Mk-0s for gentoo-amd64@lists.gentoo.org; Wed, 27 Jul 2005 12:20:02 +0200 Received: from ip68-230-97-182.ph.ph.cox.net ([68.230.97.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Jul 2005 12:20:02 +0200 Received: from 1i5t5.duncan by ip68-230-97-182.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 27 Jul 2005 12:20:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: amd64 and kernel configuration Date: Wed, 27 Jul 2005 03:13:14 -0700 Organization: Sometimes Message-ID: References: <20050727062947.73020.qmail@mail.mng.mn> <25f58b7910e09fd5453bb3ec534330d1@xsmail.com> <20050727075012.79549.qmail@mail.mng.mn> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-230-97-182.ph.ph.cox.net User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table) Sender: news X-Archives-Salt: b4a7a750-672b-4b7d-adaa-67584addcefe X-Archives-Hash: 957299257d18e183c08cba662c048710 Dulmandakh Sukhbaatar posted <20050727075012.79549.qmail@mail.mng.mn>, excerpted below, on Wed, 27 Jul 2005 15:50:12 +0800: > Thanks. How can I enable hypertransport in kernel or somewhere? Anyone > knows about NUMA? I read about it, and it seems technology for > multiprocessor systems. Thus I have single CPU, I don't need it. Right? NUMA is indeed for multi-processor systems. NUMA is Non-Uniform Memory Architecture. With AMD CPUs that have the memory controller on the same chip as the CPU, that means that each CPU can control it's own memory. If you run NUMA mode in this case (and if your BIOS is set up accordingly), the kernel will try to keep the memory for each task in the memory handled by, local to, that CPU. If either the kernel or BIOS is set to unified memory, or if you only have memory sticks in the slots for one of the CPUs, then you won't get NUMA mode and the kernel won't care what memory addresses the memory for each process lives at. AFAIK, hypertransport is automatically handled by your choice of chipset. If the chipset you configure has it, it will be enabled, if not, it won't. I was therefore a bit puzzled when you mentioned hypertransport specifically in the previous post, since I don't believe there's a specific kernel option for it. (It's possible, however, that there is and I've just forgotten about it, since it's been awhile since I reviewed the settings for the entire kernel -- I just run make oldconfig and deal with any new options in each newer kernel, and additionally do any specific tweaking I might want to try.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman in http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html -- gentoo-amd64@gentoo.org mailing list