From owner-p4-projects@FreeBSD.ORG Wed Jun 3 08:12:31 2009 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id EE8D61065674; Wed, 3 Jun 2009 08:12:30 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9E001065672 for ; Wed, 3 Jun 2009 08:12:30 +0000 (UTC) (envelope-from pgj@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 95DE28FC08 for ; Wed, 3 Jun 2009 08:12:30 +0000 (UTC) (envelope-from pgj@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id n538CUVZ004263 for ; Wed, 3 Jun 2009 08:12:30 GMT (envelope-from pgj@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id n538CUaa004261 for perforce@freebsd.org; Wed, 3 Jun 2009 08:12:30 GMT (envelope-from pgj@FreeBSD.org) Date: Wed, 3 Jun 2009 08:12:30 GMT Message-Id: <200906030812.n538CUaa004261@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to pgj@FreeBSD.org using -f From: Gabor Pali To: Perforce Change Reviews Cc: Subject: PERFORCE change 163402 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jun 2009 08:12:32 -0000 http://perforce.freebsd.org/chv.cgi?CH=163402 Change 163402 by pgj@beehive on 2009/06/03 08:12:12 IFC Affected files ... .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/config/chapter.sgml#25 integrate .. //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/mirrors/chapter.sgml#31 integrate .. //depot/projects/docproj_hu/doc/share/pgpkeys/pgpkeys-developers.sgml#26 integrate .. //depot/projects/docproj_hu/doc/share/sgml/man-refs.ent#19 integrate .. //depot/projects/docproj_hu/www/en/gnome/docs/faq2.sgml#5 integrate .. //depot/projects/docproj_hu/www/en/index.xsl#5 integrate .. //depot/projects/docproj_hu/www/en/projects/netperf/index.sgml#2 integrate .. //depot/projects/docproj_hu/www/en/releng/index.sgml#27 integrate .. //depot/projects/docproj_hu/www/share/sgml/header.ent#3 integrate .. //depot/projects/docproj_hu/www/share/sgml/templates.news-rdf.xsl#2 integrate .. //depot/projects/docproj_hu/www/share/sgml/templates.news-rss.xsl#2 integrate .. //depot/projects/docproj_hu/www/share/sgml/templates.press-rss.xsl#2 integrate .. //depot/projects/docproj_hu/www/share/sgml/templates.usergroups.xsl#2 integrate Differences ... ==== //depot/projects/docproj_hu/doc/hu_HU.ISO8859-2/books/handbook/config/chapter.sgml#25 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -741,6 +741,11 @@ &pgpkey.nemoliu; + + &a.zml; + &pgpkey.zml; + + &a.nox; &pgpkey.nox; @@ -756,11 +761,6 @@ &pgpkey.rene; - - &a.zml; - &pgpkey.zml; - - &a.avl; &pgpkey.avl; ==== //depot/projects/docproj_hu/doc/share/sgml/man-refs.ent#19 (text+ko) ==== @@ -20,7 +20,7 @@ lexicographical order by the entity (i.e., the dots used in place of special characters should not be expanded when comparing). - $FreeBSD: doc/share/sgml/man-refs.ent,v 1.486 2009/05/16 10:47:00 brueffer Exp $ + $FreeBSD: doc/share/sgml/man-refs.ent,v 1.487 2009/06/02 01:34:15 gabor Exp $ --> @@ -4723,6 +4723,7 @@ + ==== //depot/projects/docproj_hu/www/en/gnome/docs/faq2.sgml#5 (text+ko) ==== @@ -1,6 +1,6 @@ - + @@ -1105,14 +1105,13 @@

Up until GNOME 2.20, GDM would read the locale settings from /etc/login.conf or ~/.login.conf. - This was broken in 2.20, and since GDM 2.22 will use - a new locale scheme, it will not be fixed. However, all - hope is not lost. It is actually very easy to set the - locale for use with the GNOME Destop. GDM offers a - pull-down Language menu from which you can choose your - current locale. If you would rather not use this menu, - you can set the locale by adding the following to - ~/.profile:

+ This was broken in 2.20, and finally restored in GDM + 2.26.1_3.

+ +

However, GDM also offers a pull-down Language menu from which + you can choose your current locale. If you would rather not + use this menu or /etc/login.conf, you can set the + locale by adding the following to ~/.profile:

 export LANG=<locale>
@@ -1123,7 +1122,9 @@
 	      (e.g. en_US.UTF-8, es_ES.ISO8859-15, fr_FR.ISO8859-1, etc.).

 
 	    
To set the default locale for the GDM greeter, add the
-	      same environment variables to /etc/profile.

+	      same environment variables to /etc/profile or
+	      define gdm_lang to the desired locale
+	      in /etc/rc.conf.

 	  
 
         

==== //depot/projects/docproj_hu/www/en/index.xsl#5 (text+ko) ====

@@ -4,7 +4,7 @@
 
 ]>
 
-
+
 
 
   
@@ -34,6 +34,13 @@
 	      CVS, CVSup, News, Commercial Vendors, homepage, CTM, Unix"/>
 	
 	
+
     
     
     
@@ -159,6 +166,9 @@
 					ja
 				  
 				  
  • 
+					nl
+				  
    • 
+				  
  • 
 					ru
 				  
    • 
 				  
  • 

==== //depot/projects/docproj_hu/www/en/projects/netperf/index.sgml#2 (text+ko) ====

@@ -1,6 +1,6 @@
 
-
+
 
 
 
@@ -53,11 +53,10 @@
       will work toward these goals:
    
 
     
      
-      
    • Complete locking work to make sure all components of the stack
-	are able to run without the Giant lock.  While most of the network
-	stack, especially mainstream protocols, runs without Giant, some
-	components require Giant to be placed back over the stack if compiled
-	into the kernel, reducing parallelism.
      • 
+      
    • The Netperf project has completed locking work for all components
+	of the network stack; as of FreeBSD 7.0 we have removed non-MPSAFE
+	protocol shims, and as of FreeBSD 8.0 we have removed non-MPSAFE
+	device driver shims.
      • 
 
       
    • Optimize locking strategies to find better balances between
 	locking granularity and locking overhead.  In the first cut at locking
@@ -126,7 +125,8 @@
 	increasing effective CPU utilization and hence throughput.  For
 	example, introducing additional netisr threads capable of running on
 	more than one CPU at a time can increase input parallelism, subject
-	to maintaining desirable packet ordering.
      • 
+	to maintaining desirable packet ordering (present in FreeBSD
+	8.0).
      
     
    
 
     
@@ -204,13 +204,12 @@
       
 	 Employ queued dispatch across netisr dispatch API 
 	 &a.rwatson; 
-	 20041124 
-	 &status.prototyped; 
-	 Pull all of the mbufs in the netisr ifqueue out of the ifqueue
-	  into a thread-local mbuf queue to avoid repeated lock operations
-	  to access the queue.  Also use lock-free operations to test for
-	  queue contents being present.  This has been prototyped in the
-	  rwatson_netperf branch. 
+	 20090601 
+	 &status.done 
+	 Pull all of the mbufs in the netisr queue into a thread-local
+	  mbuf queue to avoid repeated lock operations to access the queue.
+	  This work was completed as part of the netisr2 project, and will
+	  ship with 8.0-RELEASE. 
       
 
       
@@ -247,8 +246,8 @@
 	  critical sections to synchronize access instead of a mutex.  While
 	  malloc(9) is less frequently used in the network stack than uma(9),
 	  it is used for socket address data, so is on performance critical
-	  paths for datagram operations.  This has been committed and will
-	  appear in 6.0-RELEASE. 
+	  paths for datagram operations.  This has been committed and appeared
+	  6.0-RELEASE. 
       
 
       
@@ -266,11 +265,11 @@
 	  cost of critical sections in the common case by avoiding expensive
 	  microcode operations on the CPU.  By restoring this model, or a
 	  variation on it, critical sections can be made substantially
-	  cheaper to enter.  In particular, this change will lower the cost
+	  cheaper to enter.  In particular, this change lowers the cost
 	  of critical sections on UP such that it is approximately the same
 	  cost as a mutex, meaning that optimizations on SMP to use critical
 	  sections instead of mutexes will not harm UP performance.  This
-	  change has now been committed, and will appear in 6.0-RELEASE. 
+	  change has now been committed, and appeared in 6.0-RELEASE. 
       
 
       
@@ -296,26 +295,41 @@
       
 	 Add true inpcb reference count support 
 	 &a.mohans;, &a.rwatson;, &a.peter; 
-	 20060412 
-	 &status.new; 
-	 Currently, the in-bound TCP and UDP socket paths rely on the
+	 20081208 
+	 &status.done; 
+	 Historically, the in-bound TCP and UDP socket paths relied on
 	  global pcbinfo info locks to prevent PCBs being delivered to from
 	  being garbage collected by another thread while in use.  This set
 	  of changes introduces a true reference model for PCBs so that the
-	  global lock can be released during in-bound process.
+	  global lock can be released during in-bound process, and appear
+	  in 8.0-RELEASE./td>
       
 
       
 	 Fine-grained locking for UNIX domain sockets 
 	 &a.rwatson; 
-	 20060416 
-	 &status.prototyped; 
-	 Currently, UNIX domain sockets in FreeBSD 5.x and 6.x use a
-	  single global subsystem lock.  This is sufficient to allow it to
-	  run without Giant, but results in contention with large numbers
-	  of processors simultaneously operating on UNIX domain sockets.
-	  This task introduces per-protocol control block locks in order
-	  to reduce contention on a larger subsystem lock. 
+	 20070226 
+	 &status.done; 
+	 UNIX domain sockets in FreeBSD 5.x and 6.x use a single global
+	  subsystem lock.  This is sufficient to allow it to run without
+	  Giant, but results in contention with large numbers of processors
+	  simultaneously operating on UNIX domain sockets.  This task
+	  introduced per-protocol control block locks in order to reduce
+	  contention on a larger subsystem lock, and the results appeared in
+	  7.0-RELEASE. 
+      
+
+      
+	 Multiple netisr threads 
+	 &a.rwatson; 
+	 20090601 
+	 &status.done; 
+	 Historically, the BSD network stack has used a single network
+	  software interrupt context, for deferred network processing.  With
+	  the introduction of multi-processing, this became a single
+	  software interrupt thread.  In FreeBSD 8.0, multiple netisr
+	  threads are now supported, up to the number of CPUs present in the
+	  system.
       
 
     

==== //depot/projects/docproj_hu/www/en/releng/index.sgml#27 (text+ko) ====

@@ -1,6 +1,6 @@
 
-
+
 
 
 
@@ -56,7 +56,7 @@
     
       August 2009
       FreeBSD 8.0
-       
+      code slush since June 1st
     
   
 

==== //depot/projects/docproj_hu/www/share/sgml/header.ent#3 (text+ko) ====

@@ -1,4 +1,4 @@
-
+
 
 
 
@@ -46,12 +46,26 @@
 
   
+
   
   '>
 ]]>
 
   
+
   
   '>
 

==== //depot/projects/docproj_hu/www/share/sgml/templates.news-rdf.xsl#2 (text+ko) ====

@@ -5,14 +5,14 @@
 
 ]>
 
-
+
 
 
 
   
   
-  
+  
 
   
     

==== //depot/projects/docproj_hu/www/share/sgml/templates.news-rss.xsl#2 (text+ko) ====

@@ -7,7 +7,7 @@
 
 ]>
 
-
+
 
 
   
-  
+  
 
   
     

==== //depot/projects/docproj_hu/www/share/sgml/templates.press-rss.xsl#2 (text+ko) ====

@@ -7,7 +7,7 @@
 
 ]>
 
-
+
 
 
+
 
 
   
 
-