From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: GC: cons sweeping and cons block size Date: Wed, 04 Jul 2007 21:29:47 -0400 Message-ID: References: <200707031622.10136.jyavner@member.fsf.org> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1183599010 15435 80.91.229.12 (5 Jul 2007 01:30:10 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 5 Jul 2007 01:30:10 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jonathan Yavner Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 05 03:30:09 2007 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1I6GAW-0004D5-Kv for ged-emacs-devel@m.gmane.org; Thu, 05 Jul 2007 03:30:04 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I6GAW-0004jl-4l for ged-emacs-devel@m.gmane.org; Wed, 04 Jul 2007 21:30:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I6GAL-0004W1-23 for emacs-devel@gnu.org; Wed, 04 Jul 2007 21:29:53 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I6GAJ-0004Th-H2 for emacs-devel@gnu.org; Wed, 04 Jul 2007 21:29:52 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I6GAJ-0004Sx-BO for emacs-devel@gnu.org; Wed, 04 Jul 2007 21:29:51 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I6GAF-0003iV-UZ; Wed, 04 Jul 2007 21:29:48 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1I6GAF-0006NW-Lz; Wed, 04 Jul 2007 21:29:47 -0400 In-reply-to: <200707031622.10136.jyavner@member.fsf.org> (message from Jonathan Yavner on Tue, 3 Jul 2007 16:22:09 -0400) X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:74312 Archived-At: On some systems, large malloc blocks go directly to MMAP_ANONYMOUS and so fragmentation worries are eliminated. I don't see any support for direct use of mmap() in gmalloc.c, though. Allocation of buffer contents has code to use mmap. I don't think anything else Emacs allocates is likely to be very large. (In GNU we reject the Unix convention of writing `()' after a function name. `mmap()' is not a function, it is a function call with no arguments.)