From owner-svn-src-all@FreeBSD.ORG Fri Mar 19 13:19:27 2010 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E885106566B; Fri, 19 Mar 2010 13:19:27 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6EE088FC2A; Fri, 19 Mar 2010 13:19:27 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 0DCA046B09; Fri, 19 Mar 2010 09:19:27 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 653D38A01F; Fri, 19 Mar 2010 09:19:26 -0400 (EDT) From: John Baldwin To: Hiroki Sato Date: Fri, 19 Mar 2010 08:22:03 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <201003190920.o2J9K6oD003965@svn.freebsd.org> In-Reply-To: <201003190920.o2J9K6oD003965@svn.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201003190822.03584.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Fri, 19 Mar 2010 09:19:26 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: svn-src-releng@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r205311 - releng/7.3/release/doc/en_US.ISO8859-1/relnotes X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2010 13:19:27 -0000 On Friday 19 March 2010 5:20:06 am Hiroki Sato wrote: > --- releng/7.3/release/doc/en_US.ISO8859-1/relnotes/article.sgml Fri Mar 19 05:40:47 2010 (r205310) > +++ releng/7.3/release/doc/en_US.ISO8859-1/relnotes/article.sgml Fri Mar 19 09:20:06 2010 (r205311) Just a couple of notes: > @@ -151,13 +151,35 @@ > > Kernel Changes > > + The &man.acpi.4; subsystem now supports parsing SRAT > + (System Resource Affinity Table used to describe affinity > + relationships between CPUs and memory. This is probably a bit of an overstatement. We only support examining it via acpidump(8). We do not support using it in the kernel to provide NUMA support (I have some WIP for this, but it's not even in HEAD yet). > + The &os; virtual memory > + subsystem now supports fully transparent use of > + superpages for application memory; > + application memory pages are dynamically promoted to or > + demoted from superpages without any modification to > + application code. This change offers the benefit of large > + page sizes such as improved virtual memory efficiency and > + reduced TLB (translation lookaside buffer) misses without > + downsides like application changes and virtual memory > + inflexibility. This can be enabled by setting a loader tunable > + vm.pmap.pg_ps_enabled to > + 1 and is enabled by default on > + &arch.amd64;. Hmm, I thought superpages was actually present in 7.2 as well, the only change in 7.3 was to enable it by default (which was subsequently reverted). Note that it is not enabled by default for 7.3, so that part should be updated, though this entire paragraph is perhaps not relevant for 7.3. Also, I think this paragraph isn't quite right: The &man.pci.4; subsystem now supports proxying of PCI Express MSI/MSI-X (Message Signaled Interrupt) requests and bus interrupt requests for child devices. This allows child devices to use MSI/MSI-X interrupts. My guess is that this is actually describing changes made to the vgapci(4) driver so that child devices such as drm(4) can use MSI? Also, MSI is not PCI-e specific, so I would just say 'PCI MSI/MSI-X (...) requests'. -- John Baldwin