History log of /dragonfly/sys/cpu/x86_64/include/lwbuf.h (Results 1 – 6 of 6)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3, v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0
# 68ad1455 16-Sep-2012 Matthew Dillon <dillon@apollo.backplane.com>

kernel - Add vm.read_shortcut_enable

* Add vm.read_shortcut_enable (disabled by default for now). Set to 1 to
enable this feature.

This enables a helper function which HAMMER1 now uses to shor

kernel - Add vm.read_shortcut_enable

* Add vm.read_shortcut_enable (disabled by default for now). Set to 1 to
enable this feature.

This enables a helper function which HAMMER1 now uses to short-cut read()
operations on files. This feature only works on x86-64.

* When enabled this feature allows file read() requests to be satisfied
directly from the VM page cache using lwbuf's, completely bypassing the
buffer cache and also bypassing most of the VFS's VOP_READ code.

The result is an approximate doubling of read() performance in cases
where the buffer cache is too small to fit the hot data set, but the VM
page cache is not.

This feature is able to avoid the buffer cache and thus prevent buffer
cycling within it which, due to the constant installation and
deinstallation of pages in KVM cause a great deal of SMP page table
page invalidations.

show more ...


Revision tags: v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0
# 86d7f5d3 26-Nov-2011 John Marino <draco@marino.st>

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.


Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0
# a8a94599 07-Feb-2011 Sascha Wildner <saw@online.de>

Remove useless belt and suspenders include guards in some of our headers.

For these headers:

/usr/include/machine/atomic.h
/usr/include/machine/bus_dma.h
/usr/include/machine/coredump.h
/usr/includ

Remove useless belt and suspenders include guards in some of our headers.

For these headers:

/usr/include/machine/atomic.h
/usr/include/machine/bus_dma.h
/usr/include/machine/coredump.h
/usr/include/machine/cpufunc.h
/usr/include/machine/db_machdep.h
/usr/include/machine/elf.h
/usr/include/machine/endian.h
/usr/include/machine/frame.h
/usr/include/machine/limits.h
/usr/include/machine/npx.h
/usr/include/machine/profile.h
/usr/include/machine/segments.h
/usr/include/machine/stdarg.h
/usr/include/machine/stdint.h
/usr/include/machine/trap.h
/usr/include/machine/tss.h
/usr/include/machine/ucontext.h
/usr/include/machine/vframe.h
/usr/include/machine/vm86.h

All these headers #define _CPU_... and not _MACHINE_... even though they
are in /usr/include/machine. And the headers themselves have include
guards already. So there's little point in having them around the actual
#include additionally.

show more ...


# 7a683a24 20-Jan-2011 Matthew Dillon <dillon@apollo.backplane.com>

kernel - Optimize the x86-64 lwbuf API

* Change lwbuf_alloc(m) to lwbuf_alloc(m, &lwb_cache), passing a pointer to
a struct lwb which lwbuf_alloc() may used if it desires.

* The x86-64 lwbuf_allo

kernel - Optimize the x86-64 lwbuf API

* Change lwbuf_alloc(m) to lwbuf_alloc(m, &lwb_cache), passing a pointer to
a struct lwb which lwbuf_alloc() may used if it desires.

* The x86-64 lwbuf_alloc() now just fills in the passed lwb and returns it.
The i386 lwbuf_alloc() still uses the objcache w/ its kva mappings. This
removes objcache calls from the critical path.

* The x86-64 lwbuf_alloc()/lwbuf_free() functions are now inlines (ALL x86-64
lwbuf functions are now inlines).

show more ...


Revision tags: v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0
# 46751036 19-Mar-2010 Samuel J. Greear <sjg@thesjg.com>

kernel - Include headers declaring vm_page_t in lwbuf headers

This commit unbreaks buildworld on i386.

Reported-by: Jan Lentfer


# 5c5185ae 09-Mar-2010 Samuel J. Greear <sjg@thesjg.com>

kernel - Introduce lightweight buffers

* Summary:
The lightweight buffer (lwbuf) subsystem is effectively a reimplementation
of the sfbuf (sendfile buffers) implementation. It was designed to

kernel - Introduce lightweight buffers

* Summary:
The lightweight buffer (lwbuf) subsystem is effectively a reimplementation
of the sfbuf (sendfile buffers) implementation. It was designed to be
lighter weight than the sfbuf implementation when possible, on x86_64
we use the DMAP and the implementation is -very- simple. It was also
designed to be more SMP friendly.

* Replace all consumption of sfbuf with lwbuf

* Refactor sfbuf to act as an external refcount mechanism for sendfile(2),
this will probably go away eventually as well.

show more ...