From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from twinlark.arctic.org (twinlark.arctic.org [204.62.130.91]) by kvack.org (8.8.7/8.8.7) with SMTP id QAA28138 for ; Thu, 25 Jun 1998 16:08:19 -0400 Date: Thu, 25 Jun 1998 13:31:59 -0700 (PDT) From: Dean Gaudet Subject: Re: Thread implementations... In-Reply-To: <199806251135.MAA00851@dax.dcs.ed.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org To: "Stephen C. Tweedie" Cc: "Eric W. Biederman" , Richard Gooch , linux-kernel@vger.rutgers.edu, linux-mm@kvack.org List-ID: On Thu, 25 Jun 1998, Stephen C. Tweedie wrote: > Hi, > > On 24 Jun 1998 23:56:28 -0500, ebiederm+eric@npwt.net (Eric > W. Biederman) said: > > > mmap, madvise(SEQUENTIAL),write > > is easy to implement. The mmap layer already does readahead, all we > > do is tell it not to be so conservative. > > Swap readhead is also now possible. However, madvise(SEQUENTIAL) needs > to do much more than this; it needs to aggressively track what region of > the vma is being actively used, and to unmap those areas no longer in > use. Remember it's *regions* not just a region. An http/ftp server sends the same file over and over and over. There are many cursors moving sequentially within the same file. A threaded http/ftp server will have a single mmap, and multiple users of that mmap. Dean