#
ea2d874c |
|
03-May-2024 |
Matthew Grooms <mgrooms@shrew.net> |
geom_stripe: Cascade cantrim just like we do for gmirror If any of the disks can support trim, cascade that up the stack. Otherwise, trims won't pass through striped raid setups. PR: 277673 Reviewed by: imp (minor style tweaks from bug report)
|
#
fdafd315 |
|
24-Nov-2023 |
Warner Losh <imp@FreeBSD.org> |
sys: Automated cleanup of cdefs and other formatting Apply the following automated changes to try to eliminate no-longer-needed sys/cdefs.h includes as well as now-empty blank lines in a row. Remove /^#if.*\n#endif.*\n#include\s+<sys/cdefs.h>.*\n/ Remove /\n+#include\s+<sys/cdefs.h>.*\n+#if.*\n#endif.*\n+/ Remove /\n+#if.*\n#endif.*\n+/ Remove /^#if.*\n#endif.*\n/ Remove /\n+#include\s+<sys/cdefs.h>\n#include\s+<sys/types.h>/ Remove /\n+#include\s+<sys/cdefs.h>\n#include\s+<sys/param.h>/ Remove /\n+#include\s+<sys/cdefs.h>\n#include\s+<sys/capsicum.h>/ Sponsored by: Netflix
|
#
685dc743 |
|
16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
sys: Remove $FreeBSD$: one-line .c pattern Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
|
#
4d846d26 |
|
10-May-2023 |
Warner Losh <imp@FreeBSD.org> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause. Discussed with: pfg MFC After: 3 days Sponsored by: Netflix
|
#
10ae42cc |
|
29-Jan-2022 |
Alexander Motin <mav@FreeBSD.org> |
GEOM: Set G_CF_DIRECT_SEND/RECEIVE for taste consumers. All I/O requests through the taste consumers are synchronous, done with g_read_data() and without any locks held. It makes no sense to delegate the I/O to g_down/g_up threads. This removes many of context switches during disk retaste. MFC after: 2 weeks
|
#
739a9c51 |
|
13-Dec-2021 |
Edward Tomasz Napierala <trasz@FreeBSD.org> |
geom(4): Fix some of the "set but not used" warnings The few I've left in place look like potential bugs. Sponsored By: EPSRC
|
#
c2da9542 |
|
10-Aug-2021 |
Alexander Motin <mav@FreeBSD.org> |
geom(4): Mark all sysctls as CTLFLAG_MPSAFE. This code does not use Giant lock for very long time. MFC after: 2 weeks
|
#
cd853791 |
|
27-Nov-2020 |
Konstantin Belousov <kib@FreeBSD.org> |
Make MAXPHYS tunable. Bump MAXPHYS to 1M. Replace MAXPHYS by runtime variable maxphys. It is initialized from MAXPHYS by default, but can be also adjusted with the tunable kern.maxphys. Make b_pages[] array in struct buf flexible. Size b_pages[] for buffer cache buffers exactly to atop(maxbcachebuf) (currently it is sized to atop(MAXPHYS)), and b_pages[] for pbufs is sized to atop(maxphys) + 1. The +1 for pbufs allow several pbuf consumers, among them vmapbuf(), to use unaligned buffers still sized to maxphys, esp. when such buffers come from userspace (*). Overall, we save significant amount of otherwise wasted memory in b_pages[] for buffer cache buffers, while bumping MAXPHYS to desired high value. Eliminate all direct uses of the MAXPHYS constant in kernel and driver sources, except a place which initialize maxphys. Some random (and arguably weird) uses of MAXPHYS, e.g. in linuxolator, are converted straight. Some drivers, which use MAXPHYS to size embeded structures, get private MAXPHYS-like constant; their convertion is out of scope for this work. Changes to cam/, dev/ahci, dev/ata, dev/mpr, dev/mpt, dev/mvs, dev/siis, where either submitted by, or based on changes by mav. Suggested by: mav (*) Reviewed by: imp, mav, imp, mckusick, scottl (intermediate versions) Tested by: pho Sponsored by: The FreeBSD Foundation Differential revision: https://reviews.freebsd.org/D27225
|
#
d22ff249 |
|
18-Oct-2020 |
Edward Tomasz Napierala <trasz@FreeBSD.org> |
Make g_attach() return ENXIO for orphaned providers; update various classes to add missing error checking. Reviewed by: imp MFC after: 2 weeks Sponsored by: NetApp, Inc. Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D26658
|
#
fcf69f3d |
|
21-Jul-2020 |
Xin LI <delphij@FreeBSD.org> |
Consistently use gctl_get_provider instead of home-grown variants. Reviewed by: cem, imp MFC after: 2 weeks Differential revision: https://reviews.freebsd.org/D25739
|
#
8510f61a |
|
08-Jul-2020 |
Xin LI <delphij@FreeBSD.org> |
sys/geom: consistently use _PATH_DEV instead of hardcoding "/dev/". Reviewed by: cem MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D25565
|
#
7029da5c |
|
26-Feb-2020 |
Pawel Biernacki <kaktus@FreeBSD.org> |
Mark more nodes as CTLFLAG_MPSAFE or CTLFLAG_NEEDGIANT (17 of many) r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are still not MPSAFE (or already are but aren’t properly marked). Use it in preparation for a general review of all nodes. This is non-functional change that adds annotations to SYSCTL_NODE and SYSCTL_PROC nodes using one of the soon-to-be-required flags. Mark all obvious cases as MPSAFE. All entries that haven't been marked as MPSAFE before are by default marked as NEEDGIANT Approved by: kib (mentor, blanket) Commented by: kib, gallatin, melifaro Differential Revision: https://reviews.freebsd.org/D23718
|
#
fd99699d |
|
27-Jan-2020 |
Konstantin Belousov <kib@FreeBSD.org> |
Fix aggregating geoms for BIO_SPEEDUP. If the bio was split into several bios going down, completion computes bio_completed of the original bio as sum of the bio_completes of the splits. For BIO_SETUP, bio_length means something different than the length. it is the requested speedup amount, and is duplicated into the splits, which is in fact reasonable, since we cannot know how the previous activity was distributed among subordinate geoms. Obviously, the sum of n bio_length is greater than bio_length for n > 1, which triggers assert that bio_length >= bio_completed for e.g. geom_stripe and geom_raid3. Fix this by reassigning bio_completed from bio_length for completed BIO_SPEEDED, I do not think it really mattters what we return in bio_completed. Reported and tested by: pho Reviewed by: imp MFC after: 1 week Differential revision: https://reviews.freebsd.org/D23380
|
#
8b522bda |
|
16-Jan-2020 |
Warner Losh <imp@FreeBSD.org> |
Pass BIO_SPEEDUP through all the geom layers While some geom layers pass unknown commands down, not all do. For the ones that don't, pass BIO_SPEEDUP down to the providers that constittue the geom, as applicable. No changes to vinum or virstor because I was unsure how to add this support, and I'm also unsure how to test these. gvinum doesn't implement BIO_FLUSH either, so it may just be poorly maintained. gvirstor is for testing and not supportig BIO_SPEEDUP is fine. Reviewed by: chs Differential Revision: https://reviews.freebsd.org/D23183
|
#
ac03832e |
|
07-Aug-2019 |
Conrad Meyer <cem@FreeBSD.org> |
GEOM: Reduce unnecessary log interleaving with sbufs Similar to what was done for device_printfs in r347229. Convert g_print_bio() to a thin shim around g_format_bio(), which acts on an sbuf; documented in g_bio.9. Reviewed by: markj Discussed with: rlibby Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D21165
|
#
49ee0fce |
|
19-Jun-2019 |
Alexander Motin <mav@FreeBSD.org> |
Use sbuf_cat() in GEOM confxml generation. When it comes to megabytes of text, difference between sbuf_printf() and sbuf_cat() becomes substantial. MFC after: 2 weeks Sponsored by: iXsystems, Inc.
|
#
6d305ab0 |
|
27-Oct-2018 |
Eugene Grosbein <eugen@FreeBSD.org> |
Extend stripeoffset and stripesize of GEOMs from u_int to off_t GEOM's stripeoffset overflows at 4 gigabyte margin (2^32) because of its u_int type. This leads to incorrect data in the output generated by "sysctl kern.geom.confxml" command, "graid list" etc. when GEOM array has volumes larger than 4G, for example. This change does not affect ABI but changes KBI. No MFC planned. Differential Revision: https://reviews.freebsd.org/D13426
|
#
74d6c131 |
|
10-Apr-2018 |
Kyle Evans <kevans@FreeBSD.org> |
Annotate geom modules with MODULE_VERSION GEOM ELI may double ask the password during boot. Once at loader time, and once at init time. This happens due a module loading bug. By default GEOM ELI caches the password in the kernel, but without the MODULE_VERSION annotation, the kernel loads over the kernel module, even if the GEOM ELI was compiled into the kernel. In this case, the newly loaded module purges/invalidates/overwrites the GEOM ELI's password cache, which causes the double asking. MFC Note: There's a pc98 component to the original submission that is omitted here due to pc98 removal in head. This part will need to be revived upon MFC. Reviewed by: imp Submitted by: op Obtained from: opBSD MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D14992
|
#
3728855a |
|
27-Nov-2017 |
Pedro F. Giffuni <pfg@FreeBSD.org> |
sys/geom: adoption of SPDX licensing ID tags. Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task. The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
|
#
8b64f3ca |
|
23-Sep-2016 |
Alexander Motin <mav@FreeBSD.org> |
Use g_wither_provider() where applicable. It is just a helper function combining G_PF_WITHER setting with g_orphan_provider().
|
#
af3b2549 |
|
27-Jun-2014 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Pull in r267961 and r267973 again. Fix for issues reported will follow.
|
#
37a107a4 |
|
27-Jun-2014 |
Glen Barber <gjb@FreeBSD.org> |
Revert r267961, r267973: These changes prevent sysctl(8) from returning proper output, such as: 1) no output from sysctl(8) 2) erroneously returning ENOMEM with tools like truss(1) or uname(1) truss: can not get etype: Cannot allocate memory
|
#
3da1cf1e |
|
27-Jun-2014 |
Hans Petter Selasky <hselasky@FreeBSD.org> |
Extend the meaning of the CTLFLAG_TUN flag to automatically check if there is an environment variable which shall initialize the SYSCTL during early boot. This works for all SYSCTL types both statically and dynamically created ones, except for the SYSCTL NODE type and SYSCTLs which belong to VNETs. A new flag, CTLFLAG_NOFETCH, has been added to be used in the case a tunable sysctl has a custom initialisation function allowing the sysctl to still be marked as a tunable. The kernel SYSCTL API is mostly the same, with a few exceptions for some special operations like iterating childrens of a static/extern SYSCTL node. This operation should probably be made into a factored out common macro, hence some device drivers use this. The reason for changing the SYSCTL API was the need for a SYSCTL parent OID pointer and not only the SYSCTL parent OID list pointer in order to quickly generate the sysctl path. The motivation behind this patch is to avoid parameter loading cludges inside the OFED driver subsystem. Instead of adding special code to the OFED driver subsystem to post-load tunables into dynamically created sysctls, we generalize this in the kernel. Other changes: - Corrected a possibly incorrect sysctl name from "hw.cbb.intr_mask" to "hw.pcic.intr_mask". - Removed redundant TUNABLE statements throughout the kernel. - Some minor code rewrites in connection to removing not needed TUNABLE statements. - Added a missing SYSCTL_DECL(). - Wrapped two very long lines. - Avoid malloc()/free() inside sysctl string handling, in case it is called to initialize a sysctl from a tunable, hence malloc()/free() is not ready when sysctls from the sysctl dataset are registered. - Bumped FreeBSD version to indicate SYSCTL API change. MFC after: 2 weeks Sponsored by: Mellanox Technologies
|
#
66b92c07 |
|
10-Apr-2014 |
Alexander Motin <mav@FreeBSD.org> |
Do not increment bio_data in case of BIO_DELETE. This fixes KASSERT() panic in g_io_request().
|
#
40ea77a0 |
|
22-Oct-2013 |
Alexander Motin <mav@FreeBSD.org> |
Merge GEOM direct dispatch changes from the projects/camlock branch. 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
|
#
6472ac3d |
|
07-Nov-2011 |
Ed Schouten <ed@FreeBSD.org> |
Mark all SYSCTL_NODEs static that have no corresponding SYSCTL_DECLs. The SYSCTL_NODE macro defines a list that stores all child-elements of that node. If there's no SYSCTL_DECL macro anywhere else, there's no reason why it shouldn't be static.
|
#
0849a53f |
|
01-Nov-2011 |
Alexander Motin <mav@FreeBSD.org> |
Refactor disk disconnection and geom destruction handling sequences. 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.
|
#
5d807a0e |
|
10-Jul-2011 |
Andrey V. Elsukov <ae@FreeBSD.org> |
Include sys/sbuf.h directly. Reviewed by: pjd
|
#
c211af03 |
|
04-May-2011 |
Andrey V. Elsukov <ae@FreeBSD.org> |
Remove "for a moment" assignment. struct g_geom zeroed when allocated. MFC after: 1 week
|
#
90f2be24 |
|
26-Apr-2011 |
Alexander Motin <mav@FreeBSD.org> |
Implement relaxed comparision for hardcoded provider names to make it ignore adX/adaY difference in both directions to simplify migration to the CAM-based ATA or back.
|
#
cb08c2cc |
|
25-Feb-2011 |
Alexander Leidinger <netchild@FreeBSD.org> |
Add some FEATURE macros for various GEOM classes. No FreeBSD version bump, the userland application to query the features will be committed last and can serve as an indication of the availablility if needed. Sponsored by: Google Summer of Code 2010 Submitted by: kibab Reviewed by: silence on geom@ during 2 weeks X-MFC after: to be determined in last commit with code from this project
|
#
a7d5f7eb |
|
19-Oct-2010 |
Jamie Gritton <jamie@FreeBSD.org> |
A new jail(8) with a configuration file, to replace the work currently done by /etc/rc.d/jail.
|
#
f24bf752 |
|
18-Feb-2010 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Correct comment.
|
#
48eae87f |
|
05-Jan-2010 |
Alexander Motin <mav@FreeBSD.org> |
MFC r200933: Make geom_stripe report it's stripe size to upper layers.
|
#
f00919d2 |
|
24-Dec-2009 |
Alexander Motin <mav@FreeBSD.org> |
Make geom_stripe report it's stripe size to upper layers.
|
#
8c184a2d |
|
17-Nov-2009 |
Alexander Motin <mav@FreeBSD.org> |
MFC r196837: Remove artificial MAX_IO_SIZE constant, equal to DFLTPHYS * 2. Use MAXPHYS instead. It is NULL change for GENERIC kernel, but allows 'fast' mode to work on systems with increased MAXPHYS.
|
#
69882ff1 |
|
12-Oct-2009 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
MFC r197898: If provider is open for writing when we taste it, skip it for classes that depend on on-disk metadata. This was we won't attach to providers that are used by other classes. For example we don't want to configure partitions on da0 if it is part of gmirror, what we really want is partitions on mirror/foo. During regular work it works like this: if provider is open for writing a class receives the spoiled event from GEOM and detaches, once provider is closed the taste event is send again and class can rediscover its metadata if it is still there. This doesn't work that way when new class arrives, because GEOM gives all existing providers for it to taste, also those open for writing. Classes have to decided on their own if they want to deal with such providers (eg. geom_dev) or not (classes modified by this commit). Reported by: des, Oliver Lehmann <lehmann@ans-netz.de> Tested by: des, Oliver Lehmann <lehmann@ans-netz.de> Discussed with: phk, marcel Reviewed by: marcel Approved by: re (kib)
|
#
f8727e71 |
|
09-Oct-2009 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
If provider is open for writing when we taste it, skip it for classes that depend on on-disk metadata. This was we won't attach to providers that are used by other classes. For example we don't want to configure partitions on da0 if it is part of gmirror, what we really want is partitions on mirror/foo. During regular work it works like this: if provider is open for writing a class receives the spoiled event from GEOM and detaches, once provider is closed the taste event is send again and class can rediscover its metadata if it is still there. This doesn't work that way when new class arrives, because GEOM gives all existing providers for it to taste, also those open for writing. Classes have to decided on their own if they want to deal with such providers (eg. geom_dev) or not (classes modified by this commit). Reported by: des, Oliver Lehmann <lehmann@ans-netz.de> Tested by: des, Oliver Lehmann <lehmann@ans-netz.de> Discussed with: phk, marcel Reviewed by: marcel MFC after: 3 days
|
#
af582ea7 |
|
04-Sep-2009 |
Alexander Motin <mav@FreeBSD.org> |
Remove artificial MAX_IO_SIZE constant, equal to DFLTPHYS * 2. Use MAXPHYS instead. It is NULL change for GENERIC kernel, but allows 'fast' mode to work on systems with increased MAXPHYS.
|
#
d7f03759 |
|
19-Oct-2008 |
Ulf Lilleengen <lulf@FreeBSD.org> |
- Import the HEAD csup code which is the basis for the cvsmode work.
|
#
2616144e |
|
09-Aug-2008 |
Dag-Erling Smørgrav <des@FreeBSD.org> |
Add sbuf_new_auto as a shortcut for the very common case of creating a completely dynamic sbuf. Obtained from: Varnish MFC after: 2 weeks
|
#
041b706b |
|
04-Jun-2007 |
David Malone <dwmalone@FreeBSD.org> |
Despite several examples in the kernel, the third argument of sysctl_handle_int is not sizeof the int type you want to export. The type must always be an int or an unsigned int. Remove the instances where a sizeof(variable) is passed to stop people accidently cut and pasting these examples. In a few places this was sysctl_handle_int was being used on 64 bit types, which would truncate the value to be exported. In these cases use sysctl_handle_quad to export them and change the format to Q so that sysctl(1) can still print them.
|
#
f187490a |
|
01-Nov-2006 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Change spaces to tabs where needed.
|
#
42461fba |
|
31-Oct-2006 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Implement BIO_FLUSH handling by simply passing it down to the components. Sponsored by: home.pl
|
#
38ea96ac |
|
31-Jan-2006 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Remove trailing spaces.
|
#
5bb84bc8 |
|
31-Oct-2005 |
Robert Watson <rwatson@FreeBSD.org> |
Normalize a significant number of kernel malloc type names: - Prefer '_' to ' ', as it results in more easily parsed results in memory monitoring tools such as vmstat. - Remove punctuation that is incompatible with using memory type names as file names, such as '/' characters. - Disambiguate some collisions by adding subsystem prefixes to some memory types. - Generally prefer lower case to upper case. - If the same type is defined in multiple architecture directories, attempt to use the same name in additional cases. Not all instances were caught in this change, so more work is required to finish this conversion. Similar changes are required for UMA zone names.
|
#
a95452ee |
|
19-Aug-2005 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Avoid code duplication and implement bitcount32() function in systm.h only. Reviewed by: cperciva MFC after: 3 days
|
#
0499edf4 |
|
17-Jul-2005 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Before calling g_orphan_provider(), add G_PF_WITHER flag, so GEOM will know to destroy it. PR: kern/81758 Submitted by: trasz <trasz@buziaczek.pl> MFC after: 3 days
|
#
0a3384a8 |
|
11-May-2005 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Check return value. Found by: Coverity Prevent analysis tool
|
#
e6890985 |
|
27-Feb-2005 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
- Add md_provsize field to metadata, which will help with 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
|
#
07b9f1be |
|
16-Feb-2005 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Fix year in copyrights.
|
#
53ed4e0d |
|
08-Dec-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
- Turn off 'fast' mode by default and increase maximum memory to consume when this mode is used. - Manual page update.
|
#
201dfcf1 |
|
20-Sep-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
This is not needed anymore, it is forced in GEOM now. Actually, it can even cause some problems, because GEOM requires sectorsize to be more than 0 on first access, not on provider creation, so we can skip valid providers by doing this check here. Reported by: Divacky Roman <xdivac02@stud.fit.vutbr.cz> Sven Willenberger <sven@dmv.com>
|
#
6d7b8aec |
|
30-Aug-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Allow to configure debug level from /boot/loader.conf.
|
#
29c78ab3 |
|
25-Aug-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Skip providers with not defined sector size. Reported by: kuriyama
|
#
f0c8658d |
|
24-Aug-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Dump disk number.
|
#
a5ef629f |
|
10-Aug-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Increase default kern.geom.stripe.maxmem to 50 elements.
|
#
4ffa3fef |
|
10-Aug-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Fix one of the lastest commit. This bio_caller1 should also be changed to bio_driver1 (as all the rest). This introduced a small memory leak, but it wasn't really critical, because maximum memory for g_stripe_zone is always set, so after few requests gstripe was working in "economic" mode.
|
#
6c74f517 |
|
09-Aug-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
- Introduce option for hardcoding providers' names into metadata. 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.
|
#
7e72a708 |
|
09-Aug-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Do not use g_wither_geom(9). I doesn't work in the way which is expected here anymore (after g_wither_washer() was introduced), i.e. geom and consumer will not be immediately destroyed if possible.
|
#
5721c9c7 |
|
08-Aug-2004 |
Poul-Henning Kamp <phk@FreeBSD.org> |
Tag all geom classes in the tree with a version number.
|
#
cea36368 |
|
06-Aug-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Add and document kern.geom.stripe.fast_failed sysctl, which shows how many times "fast" mode failed.
|
#
ec704301 |
|
06-Aug-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Fields bio_caller[12] should be used by the consumer and fields bio_driver[12] should be used by the provider!
|
#
37abacd4 |
|
06-Aug-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Fix I/O leakage. We're cloning bios in g_stripe_start_fast(), but when something goes wrong while running in "fast" mode, we free all bios and falling back to "economic" mode. Freeing bios, doesn't mean decrease bio_children, so bio_inbed couldn't be equal to bio_children and request was never finished. Decrease bio_children manually when destroying bios. Reported by: Sam Lawrance <boris@brooknet.com.au>, simon
|
#
1d723f1d |
|
26-Jul-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Improve geom(8)'s 'list' command to show geoms and their providers and consumers. Teach STRIPE, CONCAT and NOP classes about this improvement.
|
#
889c5dc2 |
|
26-Jul-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Change naming scheme from /dev/<name>.stripe to /dev/stripe/<name>.
|
#
2017a9d3 |
|
26-Jul-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
M_WAITOK is ok here, while I'm using M_WAITOK later in this function.
|
#
71df0725 |
|
13-Jul-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Minor sysctl description fixes. Submitted by: simon
|
#
4c55f05b |
|
09-Jul-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Implement "FAST" mode for GEOM_STRIPE class and turn it on by default. In this mode you can setup even very small stripe size and you can be sure that only one I/O request will be send to every disks in stripe. It consumes some more memory, but if allocation fails, it will fall back to "ECONOMIC" mode. It is about 10 times faster for small stripe size than "ECONOMIC" mode and other RAID0 implementations. It is even recommended to use this mode and small stripe size, so our requests are always splitted. One can still use "ECONOMIC" mode by setting kern.geom.stripe.fast to 0. It is also possible to setup maximum memory which "FAST" mode can consume, by setting kern.geom.stripe.maxmem from /boot/loader.conf.
|
#
a2e31b8b |
|
05-Jul-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
- Add 'stop' command, which works just like 'destroy' command, but sounds less dangerous. - Update manual pages and extend examples. - Bump versions.
|
#
3fb17452 |
|
26-May-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Dump some more informations: - device state - list of used providers - total number of disks - number of disks online Prodded by: Alex Deiter <tiamat@komi.mts.ru>
|
#
b09121f9 |
|
20-May-2004 |
Pawel Jakub Dawidek <pjd@FreeBSD.org> |
Introduce STRIPE GEOM class. It implements RAID0 transformation and it is intend to be fast. Just like CONCAT class it provides manual and auto configuration methods. Supported by: Wheel - Open Technologies - http://www.wheel.pl
|