1994-05-24 10:09:53 +00:00
|
|
|
/*-
|
2017-11-20 19:43:44 +00:00
|
|
|
* SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
|
*
|
1994-05-24 10:09:53 +00:00
|
|
|
* Copyright (c) 1992, 1993
|
|
|
|
|
* The Regents of the University of California. All rights reserved.
|
|
|
|
|
*
|
|
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
|
* are met:
|
|
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
|
|
|
|
* documentation and/or other materials provided with the distribution.
|
2017-02-28 23:42:47 +00:00
|
|
|
* 3. Neither the name of the University nor the names of its contributors
|
1994-05-24 10:09:53 +00:00
|
|
|
* may be used to endorse or promote products derived from this software
|
|
|
|
|
* without specific prior written permission.
|
|
|
|
|
*
|
|
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
|
*/
|
|
|
|
|
|
1994-12-30 08:02:16 +00:00
|
|
|
#ifndef _VM_EXTERN_H_
|
|
|
|
|
#define _VM_EXTERN_H_
|
1994-08-21 07:19:45 +00:00
|
|
|
|
2013-09-20 17:06:49 +00:00
|
|
|
struct pmap;
|
1994-05-24 10:09:53 +00:00
|
|
|
struct proc;
|
|
|
|
|
struct vmspace;
|
|
|
|
|
struct vnode;
|
2013-08-07 06:21:20 +00:00
|
|
|
struct vmem;
|
1994-05-24 10:09:53 +00:00
|
|
|
|
1999-12-29 05:07:58 +00:00
|
|
|
#ifdef _KERNEL
|
2022-01-29 03:39:30 +00:00
|
|
|
#include <sys/kassert.h>
|
2022-01-28 21:14:03 +00:00
|
|
|
|
Add a new file operations hook for mmap operations. File type-specific
logic is now placed in the mmap hook implementation rather than requiring
it to be placed in sys/vm/vm_mmap.c. This hook allows new file types to
support mmap() as well as potentially allowing mmap() for existing file
types that do not currently support any mapping.
The vm_mmap() function is now split up into two functions. A new
vm_mmap_object() function handles the "back half" of vm_mmap() and accepts
a referenced VM object to map rather than a (handle, handle_type) tuple.
vm_mmap() is now reduced to converting a (handle, handle_type) tuple to a
a VM object and then calling vm_mmap_object() to handle the actual mapping.
The vm_mmap() function remains for use by other parts of the kernel
(e.g. device drivers and exec) but now only supports mapping vnodes,
character devices, and anonymous memory.
The mmap() system call invokes vm_mmap_object() directly with a NULL object
for anonymous mappings. For mappings using a file descriptor, the
descriptors fo_mmap() hook is invoked instead. The fo_mmap() hook is
responsible for performing type-specific checks and adjustments to
arguments as well as possibly modifying mapping parameters such as flags
or the object offset. The fo_mmap() hook routines then call
vm_mmap_object() to handle the actual mapping.
The fo_mmap() hook is optional. If it is not set, then fo_mmap() will
fail with ENODEV. A fo_mmap() hook is implemented for regular files,
character devices, and shared memory objects (created via shm_open()).
While here, consistently use the VM_PROT_* constants for the vm_prot_t
type for the 'prot' variable passed to vm_mmap() and vm_mmap_object()
as well as the vm_mmap_vnode() and vm_mmap_cdev() helper routines.
Previously some places were using the mmap()-specific PROT_* constants
instead. While this happens to work because PROT_xx == VM_PROT_xx,
using VM_PROT_* is more correct.
Differential Revision: https://reviews.freebsd.org/D2658
Reviewed by: alc (glanced over), kib
MFC after: 1 month
Sponsored by: Chelsio
2015-06-04 19:41:15 +00:00
|
|
|
struct cdev;
|
|
|
|
|
struct cdevsw;
|
2018-10-30 18:26:34 +00:00
|
|
|
struct domainset;
|
1995-03-16 18:17:34 +00:00
|
|
|
|
2013-08-07 06:21:20 +00:00
|
|
|
/* These operate on kernel virtual addresses only. */
|
|
|
|
|
vm_offset_t kva_alloc(vm_size_t);
|
2023-11-29 12:54:49 +00:00
|
|
|
vm_offset_t kva_alloc_aligned(vm_size_t, vm_size_t);
|
2013-08-07 06:21:20 +00:00
|
|
|
void kva_free(vm_offset_t, vm_size_t);
|
|
|
|
|
|
|
|
|
|
/* These operate on pageable virtual addresses. */
|
|
|
|
|
vm_offset_t kmap_alloc_wait(vm_map_t, vm_size_t);
|
|
|
|
|
void kmap_free_wakeup(vm_map_t, vm_offset_t, vm_size_t);
|
|
|
|
|
|
|
|
|
|
/* These operate on virtual addresses backed by memory. */
|
2022-09-22 22:09:19 +00:00
|
|
|
void *kmem_alloc_attr(vm_size_t size, int flags,
|
2010-04-09 02:39:20 +00:00
|
|
|
vm_paddr_t low, vm_paddr_t high, vm_memattr_t memattr);
|
2022-09-22 22:09:19 +00:00
|
|
|
void *kmem_alloc_attr_domainset(struct domainset *ds, vm_size_t size,
|
2018-10-30 18:26:34 +00:00
|
|
|
int flags, vm_paddr_t low, vm_paddr_t high, vm_memattr_t memattr);
|
2022-09-22 22:09:19 +00:00
|
|
|
void *kmem_alloc_contig(vm_size_t size, int flags,
|
2011-10-30 05:06:14 +00:00
|
|
|
vm_paddr_t low, vm_paddr_t high, u_long alignment, vm_paddr_t boundary,
|
2011-10-28 22:36:15 +00:00
|
|
|
vm_memattr_t memattr);
|
2022-09-22 22:09:19 +00:00
|
|
|
void *kmem_alloc_contig_domainset(struct domainset *ds, vm_size_t size,
|
2018-10-30 18:26:34 +00:00
|
|
|
int flags, vm_paddr_t low, vm_paddr_t high, u_long alignment,
|
|
|
|
|
vm_paddr_t boundary, vm_memattr_t memattr);
|
2022-09-22 22:09:19 +00:00
|
|
|
void *kmem_malloc(vm_size_t size, int flags);
|
|
|
|
|
void *kmem_malloc_domainset(struct domainset *ds, vm_size_t size,
|
2018-10-30 18:26:34 +00:00
|
|
|
int flags);
|
2022-09-22 22:09:19 +00:00
|
|
|
void kmem_free(void *addr, vm_size_t size);
|
2013-08-07 06:21:20 +00:00
|
|
|
|
|
|
|
|
/* This provides memory for previously allocated address space. */
|
|
|
|
|
int kmem_back(vm_object_t, vm_offset_t, vm_size_t, int);
|
2018-01-12 23:13:55 +00:00
|
|
|
int kmem_back_domain(int, vm_object_t, vm_offset_t, vm_size_t, int);
|
2013-08-07 06:21:20 +00:00
|
|
|
void kmem_unback(vm_object_t, vm_offset_t, vm_size_t);
|
|
|
|
|
|
|
|
|
|
/* Bootstrapping. */
|
2018-07-19 20:00:28 +00:00
|
|
|
void kmem_bootstrap_free(vm_offset_t, vm_size_t);
|
2020-08-17 13:02:01 +00:00
|
|
|
void kmem_subinit(vm_map_t, vm_map_t, vm_offset_t *, vm_offset_t *, vm_size_t,
|
|
|
|
|
bool);
|
2013-08-07 06:21:20 +00:00
|
|
|
void kmem_init(vm_offset_t, vm_offset_t);
|
|
|
|
|
void kmem_init_zero_region(void);
|
|
|
|
|
void kmeminit(void);
|
|
|
|
|
|
2024-05-10 20:43:56 +00:00
|
|
|
bool kernacc(void *, int, int);
|
|
|
|
|
bool useracc(void *, int, int);
|
2019-09-27 18:43:36 +00:00
|
|
|
int vm_fault(vm_map_t map, vm_offset_t vaddr, vm_prot_t fault_type,
|
|
|
|
|
int fault_flags, vm_page_t *m_hold);
|
2009-07-03 22:17:37 +00:00
|
|
|
void vm_fault_copy_entry(vm_map_t, vm_map_t, vm_map_entry_t, vm_map_entry_t,
|
|
|
|
|
vm_ooffset_t *);
|
2011-07-09 15:21:10 +00:00
|
|
|
int vm_fault_disable_pagefaults(void);
|
|
|
|
|
void vm_fault_enable_pagefaults(int save);
|
2010-12-25 21:26:56 +00:00
|
|
|
int vm_fault_quick_hold_pages(vm_map_t map, vm_offset_t addr, vm_size_t len,
|
|
|
|
|
vm_prot_t prot, vm_page_t *ma, int max_count);
|
2019-09-27 18:43:36 +00:00
|
|
|
int vm_fault_trap(vm_map_t map, vm_offset_t vaddr, vm_prot_t fault_type,
|
|
|
|
|
int fault_flags, int *signo, int *ucode);
|
Add a new file operations hook for mmap operations. File type-specific
logic is now placed in the mmap hook implementation rather than requiring
it to be placed in sys/vm/vm_mmap.c. This hook allows new file types to
support mmap() as well as potentially allowing mmap() for existing file
types that do not currently support any mapping.
The vm_mmap() function is now split up into two functions. A new
vm_mmap_object() function handles the "back half" of vm_mmap() and accepts
a referenced VM object to map rather than a (handle, handle_type) tuple.
vm_mmap() is now reduced to converting a (handle, handle_type) tuple to a
a VM object and then calling vm_mmap_object() to handle the actual mapping.
The vm_mmap() function remains for use by other parts of the kernel
(e.g. device drivers and exec) but now only supports mapping vnodes,
character devices, and anonymous memory.
The mmap() system call invokes vm_mmap_object() directly with a NULL object
for anonymous mappings. For mappings using a file descriptor, the
descriptors fo_mmap() hook is invoked instead. The fo_mmap() hook is
responsible for performing type-specific checks and adjustments to
arguments as well as possibly modifying mapping parameters such as flags
or the object offset. The fo_mmap() hook routines then call
vm_mmap_object() to handle the actual mapping.
The fo_mmap() hook is optional. If it is not set, then fo_mmap() will
fail with ENODEV. A fo_mmap() hook is implemented for regular files,
character devices, and shared memory objects (created via shm_open()).
While here, consistently use the VM_PROT_* constants for the vm_prot_t
type for the 'prot' variable passed to vm_mmap() and vm_mmap_object()
as well as the vm_mmap_vnode() and vm_mmap_cdev() helper routines.
Previously some places were using the mmap()-specific PROT_* constants
instead. While this happens to work because PROT_xx == VM_PROT_xx,
using VM_PROT_* is more correct.
Differential Revision: https://reviews.freebsd.org/D2658
Reviewed by: alc (glanced over), kib
MFC after: 1 month
Sponsored by: Chelsio
2015-06-04 19:41:15 +00:00
|
|
|
int vm_forkproc(struct thread *, struct proc *, struct thread *,
|
|
|
|
|
struct vmspace *, int);
|
2002-03-19 22:20:14 +00:00
|
|
|
void vm_waitproc(struct proc *);
|
Add a new file operations hook for mmap operations. File type-specific
logic is now placed in the mmap hook implementation rather than requiring
it to be placed in sys/vm/vm_mmap.c. This hook allows new file types to
support mmap() as well as potentially allowing mmap() for existing file
types that do not currently support any mapping.
The vm_mmap() function is now split up into two functions. A new
vm_mmap_object() function handles the "back half" of vm_mmap() and accepts
a referenced VM object to map rather than a (handle, handle_type) tuple.
vm_mmap() is now reduced to converting a (handle, handle_type) tuple to a
a VM object and then calling vm_mmap_object() to handle the actual mapping.
The vm_mmap() function remains for use by other parts of the kernel
(e.g. device drivers and exec) but now only supports mapping vnodes,
character devices, and anonymous memory.
The mmap() system call invokes vm_mmap_object() directly with a NULL object
for anonymous mappings. For mappings using a file descriptor, the
descriptors fo_mmap() hook is invoked instead. The fo_mmap() hook is
responsible for performing type-specific checks and adjustments to
arguments as well as possibly modifying mapping parameters such as flags
or the object offset. The fo_mmap() hook routines then call
vm_mmap_object() to handle the actual mapping.
The fo_mmap() hook is optional. If it is not set, then fo_mmap() will
fail with ENODEV. A fo_mmap() hook is implemented for regular files,
character devices, and shared memory objects (created via shm_open()).
While here, consistently use the VM_PROT_* constants for the vm_prot_t
type for the 'prot' variable passed to vm_mmap() and vm_mmap_object()
as well as the vm_mmap_vnode() and vm_mmap_cdev() helper routines.
Previously some places were using the mmap()-specific PROT_* constants
instead. While this happens to work because PROT_xx == VM_PROT_xx,
using VM_PROT_* is more correct.
Differential Revision: https://reviews.freebsd.org/D2658
Reviewed by: alc (glanced over), kib
MFC after: 1 month
Sponsored by: Chelsio
2015-06-04 19:41:15 +00:00
|
|
|
int vm_mmap(vm_map_t, vm_offset_t *, vm_size_t, vm_prot_t, vm_prot_t, int,
|
|
|
|
|
objtype_t, void *, vm_ooffset_t);
|
|
|
|
|
int vm_mmap_object(vm_map_t, vm_offset_t *, vm_size_t, vm_prot_t,
|
|
|
|
|
vm_prot_t, int, vm_object_t, vm_ooffset_t, boolean_t, struct thread *);
|
2011-07-10 20:49:13 +00:00
|
|
|
int vm_mmap_to_errno(int rv);
|
Add a new file operations hook for mmap operations. File type-specific
logic is now placed in the mmap hook implementation rather than requiring
it to be placed in sys/vm/vm_mmap.c. This hook allows new file types to
support mmap() as well as potentially allowing mmap() for existing file
types that do not currently support any mapping.
The vm_mmap() function is now split up into two functions. A new
vm_mmap_object() function handles the "back half" of vm_mmap() and accepts
a referenced VM object to map rather than a (handle, handle_type) tuple.
vm_mmap() is now reduced to converting a (handle, handle_type) tuple to a
a VM object and then calling vm_mmap_object() to handle the actual mapping.
The vm_mmap() function remains for use by other parts of the kernel
(e.g. device drivers and exec) but now only supports mapping vnodes,
character devices, and anonymous memory.
The mmap() system call invokes vm_mmap_object() directly with a NULL object
for anonymous mappings. For mappings using a file descriptor, the
descriptors fo_mmap() hook is invoked instead. The fo_mmap() hook is
responsible for performing type-specific checks and adjustments to
arguments as well as possibly modifying mapping parameters such as flags
or the object offset. The fo_mmap() hook routines then call
vm_mmap_object() to handle the actual mapping.
The fo_mmap() hook is optional. If it is not set, then fo_mmap() will
fail with ENODEV. A fo_mmap() hook is implemented for regular files,
character devices, and shared memory objects (created via shm_open()).
While here, consistently use the VM_PROT_* constants for the vm_prot_t
type for the 'prot' variable passed to vm_mmap() and vm_mmap_object()
as well as the vm_mmap_vnode() and vm_mmap_cdev() helper routines.
Previously some places were using the mmap()-specific PROT_* constants
instead. While this happens to work because PROT_xx == VM_PROT_xx,
using VM_PROT_* is more correct.
Differential Revision: https://reviews.freebsd.org/D2658
Reviewed by: alc (glanced over), kib
MFC after: 1 month
Sponsored by: Chelsio
2015-06-04 19:41:15 +00:00
|
|
|
int vm_mmap_cdev(struct thread *, vm_size_t, vm_prot_t, vm_prot_t *,
|
|
|
|
|
int *, struct cdev *, struct cdevsw *, vm_ooffset_t *, vm_object_t *);
|
|
|
|
|
int vm_mmap_vnode(struct thread *, vm_size_t, vm_prot_t, vm_prot_t *, int *,
|
|
|
|
|
struct vnode *, vm_ooffset_t *, vm_object_t *, boolean_t *);
|
2002-03-19 22:20:14 +00:00
|
|
|
void vm_set_page_size(void);
|
2009-10-21 18:38:02 +00:00
|
|
|
void vm_sync_icache(vm_map_t, vm_offset_t, vm_size_t);
|
2013-09-20 17:06:49 +00:00
|
|
|
typedef int (*pmap_pinit_t)(struct pmap *pmap);
|
|
|
|
|
struct vmspace *vmspace_alloc(vm_offset_t, vm_offset_t, pmap_pinit_t);
|
Implement global and per-uid accounting of the anonymous memory. Add
rlimit RLIMIT_SWAP that limits the amount of swap that may be reserved
for the uid.
The accounting information (charge) is associated with either map entry,
or vm object backing the entry, assuming the object is the first one
in the shadow chain and entry does not require COW. Charge is moved
from entry to object on allocation of the object, e.g. during the mmap,
assuming the object is allocated, or on the first page fault on the
entry. It moves back to the entry on forks due to COW setup.
The per-entry granularity of accounting makes the charge process fair
for processes that change uid during lifetime, and decrements charge
for proper uid when region is unmapped.
The interface of vm_pager_allocate(9) is extended by adding struct ucred *,
that is used to charge appropriate uid when allocation if performed by
kernel, e.g. md(4).
Several syscalls, among them is fork(2), may now return ENOMEM when
global or per-uid limits are enforced.
In collaboration with: pho
Reviewed by: alc
Approved by: re (kensmith)
2009-06-23 20:45:22 +00:00
|
|
|
struct vmspace *vmspace_fork(struct vmspace *, vm_ooffset_t *);
|
2007-11-05 11:36:16 +00:00
|
|
|
int vmspace_exec(struct proc *, vm_offset_t, vm_offset_t);
|
|
|
|
|
int vmspace_unshare(struct proc *);
|
2006-05-29 21:28:56 +00:00
|
|
|
void vmspace_exit(struct thread *);
|
|
|
|
|
struct vmspace *vmspace_acquire_ref(struct proc *);
|
2002-03-19 22:20:14 +00:00
|
|
|
void vmspace_free(struct vmspace *);
|
|
|
|
|
void vmspace_exitfree(struct proc *);
|
2016-01-19 21:37:51 +00:00
|
|
|
void vmspace_switch_aio(struct vmspace *);
|
2002-03-19 22:20:14 +00:00
|
|
|
void vnode_pager_setsize(struct vnode *, vm_ooffset_t);
|
2021-08-04 19:20:37 +00:00
|
|
|
void vnode_pager_purge_range(struct vnode *, vm_ooffset_t, vm_ooffset_t);
|
2004-03-15 06:42:40 +00:00
|
|
|
int vslock(void *, size_t);
|
|
|
|
|
void vsunlock(void *, size_t);
|
2005-12-16 18:34:14 +00:00
|
|
|
struct sf_buf *vm_imgact_map_page(vm_object_t object, vm_ooffset_t offset);
|
2013-08-05 08:55:35 +00:00
|
|
|
void vm_imgact_unmap_page(struct sf_buf *sf);
|
2003-06-14 23:23:55 +00:00
|
|
|
void vm_thread_dispose(struct thread *td);
|
2007-11-05 11:36:16 +00:00
|
|
|
int vm_thread_new(struct thread *td, int pages);
|
2024-04-09 19:02:12 +00:00
|
|
|
vm_pindex_t vm_kstack_pindex(vm_offset_t ks, int npages);
|
|
|
|
|
vm_object_t vm_thread_kstack_size_to_obj(int npages);
|
|
|
|
|
int vm_thread_stack_back(vm_offset_t kaddr, vm_page_t ma[], int npages,
|
|
|
|
|
int req_class, int domain);
|
2018-02-06 22:10:07 +00:00
|
|
|
u_int vm_active_count(void);
|
|
|
|
|
u_int vm_inactive_count(void);
|
|
|
|
|
u_int vm_laundry_count(void);
|
|
|
|
|
u_int vm_wait_count(void);
|
2021-12-31 04:09:08 +00:00
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Is pa a multiple of alignment, which is a power-of-two?
|
|
|
|
|
*/
|
|
|
|
|
static inline bool
|
|
|
|
|
vm_addr_align_ok(vm_paddr_t pa, u_long alignment)
|
|
|
|
|
{
|
2022-01-28 21:14:03 +00:00
|
|
|
KASSERT(powerof2(alignment), ("%s: alignment is not a power of 2: %#lx",
|
|
|
|
|
__func__, alignment));
|
2021-12-31 04:09:08 +00:00
|
|
|
return ((pa & (alignment - 1)) == 0);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* Do the first and last addresses of a range match in all bits except the ones
|
|
|
|
|
* in -boundary (a power-of-two)? For boundary == 0, all addresses match.
|
|
|
|
|
*/
|
|
|
|
|
static inline bool
|
|
|
|
|
vm_addr_bound_ok(vm_paddr_t pa, vm_paddr_t size, vm_paddr_t boundary)
|
|
|
|
|
{
|
2022-01-28 21:14:03 +00:00
|
|
|
KASSERT(powerof2(boundary), ("%s: boundary is not a power of 2: %#jx",
|
|
|
|
|
__func__, (uintmax_t)boundary));
|
2021-12-31 04:09:08 +00:00
|
|
|
return (((pa ^ (pa + size - 1)) & -boundary) == 0);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static inline bool
|
|
|
|
|
vm_addr_ok(vm_paddr_t pa, vm_paddr_t size, u_long alignment,
|
|
|
|
|
vm_paddr_t boundary)
|
|
|
|
|
{
|
|
|
|
|
return (vm_addr_align_ok(pa, alignment) &&
|
|
|
|
|
vm_addr_bound_ok(pa, size, boundary));
|
|
|
|
|
}
|
1999-12-29 05:07:58 +00:00
|
|
|
#endif /* _KERNEL */
|
These changes embody the support of the fully coherent merged VM buffer cache,
much higher filesystem I/O performance, and much better paging performance. It
represents the culmination of over 6 months of R&D.
The majority of the merged VM/cache work is by John Dyson.
The following highlights the most significant changes. Additionally, there are
(mostly minor) changes to the various filesystem modules (nfs, msdosfs, etc) to
support the new VM/buffer scheme.
vfs_bio.c:
Significant rewrite of most of vfs_bio to support the merged VM buffer cache
scheme. The scheme is almost fully compatible with the old filesystem
interface. Significant improvement in the number of opportunities for write
clustering.
vfs_cluster.c, vfs_subr.c
Upgrade and performance enhancements in vfs layer code to support merged
VM/buffer cache. Fixup of vfs_cluster to eliminate the bogus pagemove stuff.
vm_object.c:
Yet more improvements in the collapse code. Elimination of some windows that
can cause list corruption.
vm_pageout.c:
Fixed it, it really works better now. Somehow in 2.0, some "enhancements"
broke the code. This code has been reworked from the ground-up.
vm_fault.c, vm_page.c, pmap.c, vm_object.c
Support for small-block filesystems with merged VM/buffer cache scheme.
pmap.c vm_map.c
Dynamic kernel VM size, now we dont have to pre-allocate excessive numbers of
kernel PTs.
vm_glue.c
Much simpler and more effective swapping code. No more gratuitous swapping.
proc.h
Fixed the problem that the p_lock flag was not being cleared on a fork.
swap_pager.c, vnode_pager.c
Removal of old vfs_bio cruft to support the past pseudo-coherency. Now the
code doesn't need it anymore.
machdep.c
Changes to better support the parameter values for the merged VM/buffer cache
scheme.
machdep.c, kern_exec.c, vm_glue.c
Implemented a seperate submap for temporary exec string space and another one
to contain process upages. This eliminates all map fragmentation problems
that previously existed.
ffs_inode.c, ufs_inode.c, ufs_readwrite.c
Changes for merged VM/buffer cache. Add "bypass" support for sneaking in on
busy buffers.
Submitted by: John Dyson and David Greenman
1995-01-09 16:06:02 +00:00
|
|
|
#endif /* !_VM_EXTERN_H_ */
|