|
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 |
|
| #
f354e0e6 |
| 28-Mar-2020 |
Sascha Wildner <saw@online.de> |
kernel: Remove <sys/mutex.h> from all files that don't need it.
98% of these were remains from porting from FreeBSD which could have
been removed after converting to lockmgr(), etc.
While here, do
kernel: Remove <sys/mutex.h> from all files that don't need it.
98% of these were remains from porting from FreeBSD which could have
been removed after converting to lockmgr(), etc.
While here, do the same for <sys/mutex2.h>.
show more ...
|
|
Revision tags: v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3 |
|
| #
8345afad |
| 18-Jan-2020 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - Fix indefinite wait buffer bug with encrypted disks
* Preallocate all (nmax) mpipe buffers to avoid doing any large buffer
allocations inside critical low-memory I/O paths.
* Remove the
kernel - Fix indefinite wait buffer bug with encrypted disks
* Preallocate all (nmax) mpipe buffers to avoid doing any large buffer
allocations inside critical low-memory I/O paths.
* Remove the per-sector objcache, which could cause numerous blocking
memory allocations in critical low-memory I/O paths. Instead,
pre-allocate all necessary data outside of the critical path.
For now these per-sector structures are cached in a simple linked
list with a single spin-lock (not ideal).
* Reorganize per-sector data into its own essiv_ivgen_data structure,
Plus other minor cleanups.
* TODO - We need to queue the bio in the target_crypt_config structure
instead of relying on mpipe_alloc_callback() which must still allocate
a small structure via M_INTWAIT.
Reported-by: goleo, profmakx, daftaupe, others
show more ...
|
|
Revision tags: 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 |
|
| #
41a68322 |
| 26-Nov-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sys/dev/disk/dm: Remove dm_dev::dev_type
This is unused, and also not necessary.
dm core shouldn't need to be aware of target driver type.
Target dependent actions are handled by target dependent h
sys/dev/disk/dm: Remove dm_dev::dev_type
This is unused, and also not necessary.
dm core shouldn't need to be aware of target driver type.
Target dependent actions are handled by target dependent handlers.
dm targets have oop-like structure, so we don't want/need
dm core to be able to do things like below.
Also see d471f1f9 and 49784e7d.
switch (dev->dev_type) {
case DM_LINEAR_DEV:
do_something_specific_to_linear(); break;
case DM_STRIPE_DEV:
do_something_specific_to_striped(); break;
case ...:
...; break;
}
show more ...
|
| #
f603807b |
| 26-Nov-2016 |
Tomohiro Kusumi <kusumi.tomohiro@gmail.com> |
sys/dev/disk/dm: Remove dm/targets/ directory and move its entries to dm/
Device mapper targets' path
sys/dev/disk/dm/targets/<name>/dm_target_<name>.c
are too deep for no reason.
This commit remov
sys/dev/disk/dm: Remove dm/targets/ directory and move its entries to dm/
Device mapper targets' path
sys/dev/disk/dm/targets/<name>/dm_target_<name>.c
are too deep for no reason.
This commit removes targets/ directory which isn't necessary at all,
assuming userspace has no dependencies on this (and it shouldn't either).
Neither NetBSD (sys/dev/dm/dm_target_*.c) nor Linux kernel (drivers/md/dm*.c)
has a directory tree like this, which is better.
show more ...
|