History log of /dragonfly/sys/dev/raid/vinum/vinumrequest.c (Results 1 – 25 of 32)
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
# 0dcae153 26-Sep-2018 Sascha Wildner <saw@online.de>

kernel/vinum: Fix -Wundef.


Revision tags: 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
# 0c4341b9 09-Jan-2017 Matthew Dillon <dillon@apollo.backplane.com>

buf - Remove B_ORDERED, Incidental CAM MPSAFE

* Remove support for B_ORDERED. Most drivers ignore it, and it is basically
unusable.

* The CAM "xpt", "pass", and "sg" devices are MPSAFE, flag the

buf - Remove B_ORDERED, Incidental CAM MPSAFE

* Remove support for B_ORDERED. Most drivers ignore it, and it is basically
unusable.

* The CAM "xpt", "pass", and "sg" devices are MPSAFE, flag them
appropriately.

show more ...


Revision tags: 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
# 6a75dba3 20-Jun-2014 Sascha Wildner <saw@online.de>

kernel/vinum: Use %jx in a number of places instead of %llx.


Revision tags: 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
# 489fe090 07-Jan-2013 Sascha Wildner <saw@online.de>

kernel: Remove some unused variables in RAID and disk drivers.


# 9859c634 02-Jan-2013 Sascha Wildner <saw@online.de>

Remove some emacs variable settings.


Revision tags: v3.2.2, v3.2.1, v3.2.0, v3.3.0, 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, 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, v2.5.1, v2.4.1, v2.5.0, v2.4.0
# d557216f 20-Aug-2009 Matthew Dillon <dillon@apollo.backplane.com>

Fix numerous compiler warnings and format conversion specifiers.


# c2fcd54e 15-Aug-2009 Matthew Dillon <dillon@apollo.backplane.com>

VINUM - Support geometries > 2TB

* Convert remaining 32 bit block number calculations to 64 bit calculations.


# 0d0607d0 15-Aug-2009 Matthew Dillon <dillon@apollo.backplane.com>

VINUM - correct deadlock, correct 32 bit truncation, cleanup string copies

* Correct a deadlock when reading a configuration from disk via
the command line.

* Correct numerous 32 bit truncations

VINUM - correct deadlock, correct 32 bit truncation, cleanup string copies

* Correct a deadlock when reading a configuration from disk via
the command line.

* Correct numerous 32 bit truncations due to the use of min/max.

* Cleanup string copies, use ksnprintf() when possible.

show more ...


# ae8e83e6 15-Jul-2009 Matthew Dillon <dillon@apollo.backplane.com>

MPSAFE - tsleep_interlock, BUF/BIO, cluster, swap_pager.

* tsleep_interlock()/tsleep() could miss wakeups during periods of
heavy cpu activity. What would happen is code inbetween the two
calls

MPSAFE - tsleep_interlock, BUF/BIO, cluster, swap_pager.

* tsleep_interlock()/tsleep() could miss wakeups during periods of
heavy cpu activity. What would happen is code inbetween the two
calls would try to send an IPI (say, issue a wakeup()), but while
sending the IPI the kernel would be forced to process incoming IPIs
synchronous to avoid a deadlock.

The new tsleep_interlock()/tsleep() code adds another TAILQ_ENTRY to
the thread structure allowing tsleep_interlock() to formally place
the thread on the appropriate sleep queue without having to deschedule
the thread. Any wakeup which occurs between the interlock and the
real tsleep() call will remove the thread from the queue and the
later tsleep() call will recognize this and simply return without sleeping.

The new tsleep() call requires PINTERLOCKED to be passed to tsleep
so tsleep() knows that the thread has already been placed on a sleep
queue.

* Continue making BUF/BIO MPSAFE. Remove B_ASYNC and B_WANT from buf->b_flag
and add a new bio->bio_flags field to the bio. Add BIO_SYNC, BIO_WANT,
and BIO_DONE. Use atomic_cmpset_int() (aka cmpxchg) to interlock
biodone() against biowait().

vn_strategy() and dev_dstrategy() call semantics now require that
synchronous BIO's install a bio_done function and set BIO_SYNC in
the bio.

* Clean up the cluster code a bit.

* Redo the swap_pager code. Instead of issuing I/O during the collection,
which depended on critical sections to avoid races in the cluster append,
we now build the entire collection first and then dispatch the I/O.
This allows us to use only async completion for the BIOs, instead of
a hybrid sync-or-async completion.

show more ...


Revision tags: v2.3.2, v2.3.1, v2.2.1, v2.2.0, v2.3.0, v2.1.1, v2.0.1
# 00449ae2 15-Sep-2007 Sascha Wildner <swildner@dragonflybsd.org>

Fix some kprintf format warnings.


# c1a85d27 31-Jul-2007 Matthew Dillon <dillon@dragonflybsd.org>

Fix vinum. Vinum illegally uses device ops such as dev_dopen(),
dev_dclose(), and dev_dstrategy() without following the restrictions and
requirements for those calls. It does not properly check D_T

Fix vinum. Vinum illegally uses device ops such as dev_dopen(),
dev_dclose(), and dev_dstrategy() without following the restrictions and
requirements for those calls. It does not properly check D_TRACKCLOSE
and does not properly limit DMA.

Access the low level device via the vnode subsystem instead of the device
subsystem. Use new calls to synthesize appropriate vnodes based on the
requested device name and remove all the manual major/minor conversion junk.

When booting with a vinum root vinum will synthesize appropriate vnodes
to access devices. If a root mount already exists vinum will simply
open the device vnode via the filesystem.

Reported-by: "Simon 'corecode' Schubert" <bugs@crater.dragonflybsd.org>,
Chris Turner <c.turner@199technologies.org>

show more ...


# f0b5dad4 07-Jun-2007 Simon Schubert <corecode@dragonflybsd.org>

Get rid of disklabel faking/processing.


# aa336941 17-May-2007 Matthew Dillon <dillon@dragonflybsd.org>

Remove #include <sys/disklabel.h> from various source files which no longer
need it.


# b13267a5 10-Sep-2006 Matthew Dillon <dillon@dragonflybsd.org>

Change the kernel dev_t, representing a pointer to a specinfo structure,
to cdev_t. Change struct specinfo to struct cdev. The name 'cdev' was taken
from FreeBSD. Remove the dev_t shim for the ker

Change the kernel dev_t, representing a pointer to a specinfo structure,
to cdev_t. Change struct specinfo to struct cdev. The name 'cdev' was taken
from FreeBSD. Remove the dev_t shim for the kernel.

This commit generally removes the overloading of 'dev_t' between userland and
the kernel.

Also fix a bug in libkvm where a kernel dev_t (now cdev_t) was not being
properly converted to a userland dev_t.

show more ...


# fef8985e 28-Jul-2006 Matthew Dillon <dillon@dragonflybsd.org>

MASSIVE reorganization of the device operations vector. Change cdevsw
to dev_ops. dev_ops is a syslink-compatible operations vector structure
similar to the vop_ops structure used by vnodes.

Remov

MASSIVE reorganization of the device operations vector. Change cdevsw
to dev_ops. dev_ops is a syslink-compatible operations vector structure
similar to the vop_ops structure used by vnodes.

Remove a huge number of instances where a thread pointer is still being
passed as an argument to various device ops and other related routines.
The device OPEN and IOCTL calls now take a ucred instead of a thread pointer,
and the CLOSE call no longer takes a thread pointer.

show more ...


# aab4a162 09-Jul-2006 Simon Schubert <corecode@dragonflybsd.org>

Don't use B_PAGING with geteblk() bufs


# 4ef09ff8 06-Jul-2006 Simon Schubert <corecode@dragonflybsd.org>

Copy b_cmd into new buf


# 61ebc48c 05-Jul-2006 Matthew Dillon <dillon@dragonflybsd.org>

Add a missing initbufbio() to fix a panic when vinum tries to issue a
read or write.

Reported-by: Rumko, "Simon 'corecode' Schubert" <corecode@fs.ei.tum.de>


# 9a71d53f 03-May-2006 Matthew Dillon <dillon@dragonflybsd.org>

- Clarify the definitions of b_bufsize, b_bcount, and b_resid.
- Remove unnecessary assignments based on the clarified fields.
- Add additional checks for premature EOF.

b_bufsize is only used by bu

- Clarify the definitions of b_bufsize, b_bcount, and b_resid.
- Remove unnecessary assignments based on the clarified fields.
- Add additional checks for premature EOF.

b_bufsize is only used by buffer management entities such as getblk() and
other vnode-backed buffer handling procedures. b_bufsize is not required
for calls to vn_strategy() or dev_dstrategy(). A number of other subsystems
use it to track the original request size.

b_bcount is the I/O request size, but b_bcount() is allowed to be truncated
by the device chain if the request encompasses EOF (such as on a raw disk
device). A caller which needs to record the original buffer size verses
the EOF-truncated buffer can compare b_bcount after the I/O against a
recorded copy of the original request size. This copy can be recorded in
b_bufsize for unmanaged buffers (malloced or getpbuf()'d buffers).

b_resid is always relative to b_bcount, not b_bufsize. A successful read
that is truncated to the device EOF will thus have a b_resid of 0 and a
truncated b_bcount.

show more ...


# 10f3fee5 30-Apr-2006 Matthew Dillon <dillon@dragonflybsd.org>

Replace the the buffer cache's B_READ, B_WRITE, B_FORMAT, and B_FREEBUF
b_flags with a separate b_cmd field. Use b_cmd to test for I/O completion
as well (getting rid of B_DONE in the process). Thi

Replace the the buffer cache's B_READ, B_WRITE, B_FORMAT, and B_FREEBUF
b_flags with a separate b_cmd field. Use b_cmd to test for I/O completion
as well (getting rid of B_DONE in the process). This further simplifies
the setup required to issue a buffer cache I/O.

Remove a redundant header file, bus/isa/i386/isa_dma.h and merge any
discrepancies into bus/isa/isavar.h.

Give ISADMA_READ/WRITE/RAW their own independant flag definitions instead of
trying to overload them on top of B_READ, B_WRITE, and B_RAW. Add a
routine isa_dmabp() which takes a struct buf pointer and returns the ISA
dma flags associated with the operation.

Remove the 'clear_modify' argument to vfs_busy_pages(). Instead,
vfs_busy_pages() asserts that the buffer's b_cmd is valid and then uses
it to determine the action it must take.

show more ...


# a8f169e2 28-Apr-2006 Matthew Dillon <dillon@dragonflybsd.org>

Get rid of pbgetvp() and pbrelvp(). Instead fold the B_PAGING flag directly
into getpbuf() (the only type of buffer that pbgetvp() could be called on
anyway). Change related b_flags assignments fro

Get rid of pbgetvp() and pbrelvp(). Instead fold the B_PAGING flag directly
into getpbuf() (the only type of buffer that pbgetvp() could be called on
anyway). Change related b_flags assignments from '=' to '|='.

Get rid of remaining depdendancies on b_vp. vn_strategy() now relies solely
on the vp passed to it as an argument. Remove buffer cache code that sets
b_vp for anonymous pbuf's.

Add a stopgap 'vp' argument to vfs_busy_pages(). This is only really needed
by NFS and the clustering code do to the severely hackish nature of the
NFS and clustering code.

Fix a bug in the ext2fs inode code where vfs_busy_pages() was being called
on B_CACHE buffers. Add an assertion to vfs_busy_pages() to panic if it
encounters a B_CACHE buffer.

show more ...


# 591bdbe9 26-Mar-2006 Sascha Wildner <swildner@dragonflybsd.org>

struct buf's b_bcount field has been changed from long to int. Adjust
printf() formats accordingly to silence compiler warnings.


# 54078292 24-Mar-2006 Matthew Dillon <dillon@dragonflybsd.org>

Major BUF/BIO work commit. Make I/O BIO-centric and specify the disk or
file location with a 64 bit offset instead of a 32 bit block number.

* All I/O is now BIO-centric instead of BUF-centric.

*

Major BUF/BIO work commit. Make I/O BIO-centric and specify the disk or
file location with a 64 bit offset instead of a 32 bit block number.

* All I/O is now BIO-centric instead of BUF-centric.

* File/Disk addresses universally use a 64 bit bio_offset now. bio_blkno
no longer exists.

* Stackable BIO's hold disk offset translations. Translations are no longer
overloaded onto a single structure (BUF or BIO).

* bio_offset == NOOFFSET is now universally used to indicate that a
translation has not been made. The old (blkno == lblkno) junk has all
been removed.

* There is no longer a distinction between logical I/O and physical I/O.

* All driver BUFQs have been converted to BIOQs.

* BMAP, FREEBLKS, getblk, bread, breadn, bwrite, inmem, cluster_*,
and findblk all now take and/or return 64 bit byte offsets instead
of block numbers. Note that BMAP now returns a byte range for the before
and after variables.

show more ...


# 81b5c339 17-Feb-2006 Matthew Dillon <dillon@dragonflybsd.org>

Make the entire BUF/BIO system BIO-centric instead of BUF-centric. Vnode
and device strategy routines now take a BIO and must pass that BIO to
biodone(). All code which previously managed a BUF und

Make the entire BUF/BIO system BIO-centric instead of BUF-centric. Vnode
and device strategy routines now take a BIO and must pass that BIO to
biodone(). All code which previously managed a BUF undergoing I/O now
manages a BIO.

The new BIO-centric algorithms allow BIOs to be stacked, where each layer
represents a block translation, completion callback, or caller or device
private data. This information is no longer overloaded within the BUF.
Translation layer linkages remain intact as a 'cache' after I/O has completed.

The VOP and DEV strategy routines no longer make assumptions as to which
translated block number applies to them. The use the block number in the
BIO specifically passed to them.

Change the 'untranslated' constant to NOOFFSET (for bio_offset), and
(daddr_t)-1 (for bio_blkno). Rip out all code that previously set the
translated block number to the untranslated block number to indicate
that the translation had not been made.

Rip out all the cluster linkage fields for clustered VFS and clustered
paging operations. Clustering now occurs in a private BIO layer using
private fields within the BIO.

Reformulate the vn_strategy() and dev_dstrategy() abstraction(s). These
routines no longer assume that bp->b_vp == the vp of the VOP operation, and
the dev_t is no longer stored in the struct buf. Instead, only the vp passed
to vn_strategy() (and related *_strategy() routines for VFS ops), and
the dev_t passed to dev_dstrateg() (and related *_strategy() routines for
device ops) is used by the VFS or DEV code. This will allow an arbitrary
number of translation layers in the future.

Create an independant per-BIO tracking entity, struct bio_track, which
is used to determine when I/O is in-progress on the associated device
or vnode.

NOTE: Unlike FreeBSD's BIO work, our struct BUF is still used to hold
the fields describing the data buffer, resid, and error state.

Major-testing-by: Stefan Krueger

show more ...


12