summaryrefslogtreecommitdiffstats
path: root/sys/geom/concat/g_concat.h
Commit message (Collapse)AuthorAgeFilesLines
* Merge GEOM direct dispatch changes from the projects/camlock branch.mav2013-10-221-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When safety requirements are met, it allows to avoid passing I/O requests to GEOM g_up/g_down thread, executing them directly in the caller context. That allows to avoid CPU bottlenecks in g_up/g_down threads, plus avoid several context switches per I/O. The defined now safety requirements are: - caller should not hold any locks and should be reenterable; - callee should not depend on GEOM dual-threaded concurency semantics; - on the way down, if request is unmapped while callee doesn't support it, the context should be sleepable; - kernel thread stack usage should be below 50%. To keep compatibility with GEOM classes not meeting above requirements new provider and consumer flags added: - G_CF_DIRECT_SEND -- consumer code meets caller requirements (request); - G_CF_DIRECT_RECEIVE -- consumer code meets callee requirements (done); - G_PF_DIRECT_SEND -- provider code meets caller requirements (done); - G_PF_DIRECT_RECEIVE -- provider code meets callee requirements (request). Capable GEOM class can set them, allowing direct dispatch in cases where it is safe. If any of requirements are not met, request is queued to g_up or g_down thread same as before. Such GEOM classes were reviewed and updated to support direct dispatch: CONCAT, DEV, DISK, GATE, MD, MIRROR, MULTIPATH, NOP, PART, RAID, STRIPE, VFS, ZERO, ZFS::VDEV, ZFS::ZVOL, all classes based on g_slice KPI (LABEL, MAP, FLASHMAP, etc). To declare direct completion capability disk(9) KPI got new flag equivalent to G_PF_DIRECT_SEND -- DISKFLAG_DIRECT_COMPLETION. da(4) and ada(4) disk drivers got it set now thanks to earlier CAM locking work. This change more then twice increases peak block storage performance on systems with manu CPUs, together with earlier CAM locking changes reaching more then 1 million IOPS (512 byte raw reads from 16 SATA SSDs on 4 HBAs to 256 user-level threads). Sponsored by: iXsystems, Inc. MFC after: 2 months
* Refactor disk disconnection and geom destruction handling sequences.mav2011-11-011-0/+1
| | | | | | | | Do not close/destroy opened consumer directly in case of disconnect. Instead keep it existing until it will be closed in regular way in response to upstream provider destruction. Delay geom destruction in the same way. Previous implementation could destroy consumers still having active requests and worked only because of global workaround made on GEOM level.
* Remove trailing spaces.pjd2006-02-011-1/+1
|
* - Add md_provsize field to metadata, which will help withpjd2005-02-271-2/+6
| | | | | | | | | | | | | | | | | shared-last-sector problem. After this change, even if there is more than one provider with the same last sector, the proper one will be chosen based on its size. It still doesn't fix the 'c' partition problem (when da0s1 can be confused with da0s1c) and situation when 'a' partition starts at offset 0 (then da0s1a can be confused with da0s1 and da0s1c). One can use '-h' option there, when creating device or avoid sharing last sector. Actually, when providers share the same last sector and their size is equal, they provide exactly the same data, so the name (da0s1, da0s1a, da0s1c) isn't important at all. - Provide backward compatibility. - Update copyright's year. MFC after: 1 week
* - Introduce option for hardcoding providers' names into metadata.pjd2004-08-091-1/+10
| | | | | | | | | | | | It allows to fix problems when last provider's sector is shared between few providers. - Bump version number for CONCAT and STRIPE and add code for backward compatibility. - Do not bump version number of MIRROR, as it wasn't officially introduced yet. Even if someone started to play with it, there is no big deal, because wrong MD5 sum of metadata will deny those providers. - Update manual pages. - Add version history to g_(stripe|concat).h files.
* Change naming scheme from /dev/<name>.concat to /dev/concat/<name>.pjd2004-07-261-1/+1
|
* - Add 'stop' command, which works just like 'destroy' command, but soundspjd2004-07-051-1/+1
| | | | | | less dangerous. - Update manual pages and extend examples. - Bump versions.
* - Teach CONCAT class how to talk with geom(8).pjd2004-05-201-6/+10
| | | | | | | - Remove provider if any disk was lost. - Dump CONCAT version. Supported by: Wheel - Open Technologies - http://www.wheel.pl
* Print a space character between string given as a macro argument andpjd2004-03-091-0/+1
| | | | bio description.
* Correct year in copyrights.pjd2004-03-041-1/+1
|
* - Remove d_valid field, we can use d_consumer field to check if diskpjd2004-03-031-3/+0
| | | | | is valid. - Use SYSCTL_DECL() instead of using own, ugly extern.
* Removed unused fields.pjd2004-03-011-2/+0
|
* Remove unused field.pjd2004-02-271-1/+0
| | | | Approved by: scottl (mentor)
* Introduce CONCAT GEOM class for disk concatenation.pjd2004-02-191-0/+113
It allows manual and automatic (based on on-disk metadata) concatenation. Reviewed by: phk, scottl Approved by: scottl (mentor)
OpenPOWER on IntegriCloud