CVS log for src/sys/dev/raidframe/rf_dagutils.h
Up to [cvs.NetBSD.org] / src / sys / dev / raidframe
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Revision 1.22.16.1: download - view: text, markup, annotated - select for diffs
Wed Nov 4 23:22:32 2026 UTC (11 days, 7 hours ago) by perseant
Branches: perseant-exfatfs
Diff to: previous 1.22: preferred, colored; next MAIN 1.23: preferred, colored
Changes since revision 1.22: +3 -1
lines
Sync with HEAD
Revision 1.23: download - view: text, markup, annotated - select for diffs
Sat Oct 24 00:20:24 2026 UTC (3 weeks, 2 days ago) by tls
Branches: MAIN
CVS tags: perseant-exfatfs-base-20261102,
HEAD
Diff to: previous 1.22: preferred, colored
Changes since revision 1.22: +3 -1
lines
Be more conservative with pool and freelist sizes and address potential deadlocks discovered while working on PR kern/60396.
Note that with this change we track the total amount of memory allocated to
both reserved buffers and pools on a per-array basis, and constrain
"openings" to keep it under control on small-memory machines.
1) Per suggestion from oster@, rename the "emergency" freelists that are now
used before dynamic allocation to "reserved" freelists.
2) Eliminate static pool sizes and compute dynamically instead. For now,
most are larger to avoid potential deadlocks discussed below. With
some restructuring of the I/O dispatch model they can probably get smaller.
3) Address an M_WAITOK allocation with PSS_MUTEX held in "forced"
reconstruction. It appears this could deadlock rf_RaidIOThread
and the recon thread. Added another small set of emergency
buffers to cover this case.
4) Reorganize rf_Configure to initialize pools _after_ disk,
queue, and openings are determined, so each array's pools can
be sized according to the actual array geometry. Made all
sizes dynamic; but see below as to the actual constraint on
minimum pool sizes.
5) Address a potential deadlock between dispatch
and completion for the I/O and Engine threads per array if any
pool has less than "openings" minimum elements. This is because
am outbound dispatch can block in pool_get(..., PR_WAITOK) while
completed I/Os accumulate in raidPtr->iodone or term_nq.
The options are to either restructure these as two threads per
(dispatch, completion) or to grit our teeth and accept that we
must have "openings" minimum elements in each pool and on small
memory machines "openings" will thus be constrained. Elsewise,
some pools would need as little as a single page of memory.
Went for the "grit our teeth" option; a shame, but tearing the
threads apart feels like too much for now.
6) Compute bytes per opening (which can be quite large due to
emergency buffers, remembering array geometries are possible
where a stripe is much smaller than MAXPHYS) and use that to
constrain "openings" so no array allocates more than 1% of
physical memory. Comments in the reorganized rf_Configure
explain how it's done and there are some verbose and debug
printfs to let the user know what happened. With a wide array
on a low-memory machine, the bottom line is that you may be
all the way back down to openings = 6; but on big machines with
narrow arrays we can do much better.
7) Each time we configure an array, grow the global
rf_alloclist_pool to ensure it has enough space according
to array geometry and openings, so we do not block on this
pool either.
Revision 1.21.12.1: download - view: text, markup, annotated - select for diffs
Sun Aug 1 22:42:31 2021 UTC (5 years, 3 months ago) by thorpej
Branches: thorpej-i2c-spi-conf
Diff to: previous 1.21: preferred, colored; next MAIN 1.22: preferred, colored
Changes since revision 1.21: +12 -12
lines
Sync with HEAD.
Revision 1.22: download - view: text, markup, annotated - select for diffs
Fri Jul 23 00:54:45 2021 UTC (5 years, 3 months ago) by oster
Branches: MAIN
CVS tags: thorpej-ifq-base,
thorpej-ifq,
thorpej-i2c-spi-conf2-base,
thorpej-i2c-spi-conf2,
thorpej-i2c-spi-conf-base,
thorpej-futex2-base,
thorpej-futex2,
thorpej-cfargs2-base,
thorpej-cfargs2,
thorpej-altq-separation-base,
thorpej-altq-separation,
perseant-exfatfs-base-20250801,
perseant-exfatfs-base-20240630,
perseant-exfatfs-base,
netbsd-11-base,
netbsd-11-1-RELEASE,
netbsd-11-0-RELEASE,
netbsd-11-0-RC7,
netbsd-11-0-RC6,
netbsd-11-0-RC5,
netbsd-11-0-RC4,
netbsd-11-0-RC3,
netbsd-11-0-RC2,
netbsd-11-0-RC1,
netbsd-11,
netbsd-10-base,
netbsd-10-2-RELEASE,
netbsd-10-1-RELEASE,
netbsd-10-0-RELEASE,
netbsd-10-0-RC6,
netbsd-10-0-RC5,
netbsd-10-0-RC4,
netbsd-10-0-RC3,
netbsd-10-0-RC2,
netbsd-10-0-RC1,
netbsd-10,
bouyer-sunxi-drm-base,
bouyer-sunxi-drm
Branch point for: perseant-exfatfs
Diff to: previous 1.21: preferred, colored
Changes since revision 1.21: +12 -12
lines
Extensive mechanical changes to the pools used in RAIDframe.
Alloclist remains not per-RAID, so initialize that pool
separately/differently than the rest.
The remainder of pools in RF_Pools_s are now per-RAID pools. Mostly
mechanical changes to functions to allocate/destroy per-RAID pools.
Needed to make raidPtr available in certain cases to be able to find
the per-RAID pools.
Extend rf_pool_init() to now populate a per-RAID wchan value that is
unique to each pool for a given RAID device.
TODO: Complete the analysis of the minimum number of items that are
required for each pool to allow IO to progress (i.e. so that a request
for pool resources can always be satisfied), and dynamically scale
minimum pool sizes based on RAID configuration.
Revision 1.20.164.1: download - view: text, markup, annotated - select for diffs
Mon Apr 13 08:04:47 2020 UTC (6 years, 7 months ago) by martin
Branches: phil-wifi
Diff to: previous 1.20: preferred, colored; next MAIN 1.21: preferred, colored
Changes since revision 1.20: +6 -6
lines
Mostly merge changes from HEAD upto 20200411
Revision 1.21: download - view: text, markup, annotated - select for diffs
Thu Oct 10 03:43:59 2019 UTC (7 years, 1 month ago) by christos
Branches: MAIN
CVS tags: thorpej-futex-base,
thorpej-futex,
thorpej-cfargs-base,
thorpej-cfargs,
phil-wifi-20200421,
phil-wifi-20200411,
phil-wifi-20200406,
phil-wifi-20191119,
is-mlppp-base,
is-mlppp,
cjep_sun2x-base1,
cjep_sun2x-base,
cjep_sun2x,
cjep_staticlib_x-base1,
cjep_staticlib_x-base,
cjep_staticlib_x,
bouyer-xenpvh-base2,
bouyer-xenpvh-base1,
bouyer-xenpvh-base,
bouyer-xenpvh,
ad-namecache-base3,
ad-namecache-base2,
ad-namecache-base1,
ad-namecache-base,
ad-namecache
Branch point for: thorpej-i2c-spi-conf
Diff to: previous 1.20: preferred, colored
Changes since revision 1.20: +6 -6
lines
fix the function pointer and callback mess:
- callback functions return 0 and their result is not checked; make them void.
- there are two types of callbacks and they used to overload their parameters
and the callback structure; separate them into "function" and "value"
callbacks.
- make the wait function signature consistent.
Revision 1.20: download - view: text, markup, annotated - select for diffs
Sun Dec 11 12:23:37 2005 UTC (20 years, 11 months ago) by christos
Branches: MAIN
CVS tags: yamt-x86pmap-base4,
yamt-x86pmap-base3,
yamt-x86pmap-base2,
yamt-x86pmap-base,
yamt-x86pmap,
yamt-uio_vmspace-base5,
yamt-uio_vmspace,
yamt-splraiseipl-base5,
yamt-splraiseipl-base4,
yamt-splraiseipl-base3,
yamt-splraiseipl-base2,
yamt-splraiseipl-base,
yamt-splraiseipl,
yamt-pf42-baseX,
yamt-pf42-base4,
yamt-pf42-base3,
yamt-pf42-base2,
yamt-pf42-base,
yamt-pf42,
yamt-pdpolicy-base9,
yamt-pdpolicy-base8,
yamt-pdpolicy-base7,
yamt-pdpolicy-base6,
yamt-pdpolicy-base5,
yamt-pdpolicy-base4,
yamt-pdpolicy-base3,
yamt-pdpolicy-base2,
yamt-pdpolicy-base,
yamt-pdpolicy,
yamt-pagecache-tag8,
yamt-pagecache-base9,
yamt-pagecache-base8,
yamt-pagecache-base7,
yamt-pagecache-base6,
yamt-pagecache-base5,
yamt-pagecache-base4,
yamt-pagecache-base3,
yamt-pagecache-base2,
yamt-pagecache-base,
yamt-pagecache,
yamt-nfs-mp-base9,
yamt-nfs-mp-base8,
yamt-nfs-mp-base7,
yamt-nfs-mp-base6,
yamt-nfs-mp-base5,
yamt-nfs-mp-base4,
yamt-nfs-mp-base3,
yamt-nfs-mp-base2,
yamt-nfs-mp-base11,
yamt-nfs-mp-base10,
yamt-nfs-mp-base,
yamt-nfs-mp,
yamt-lazymbuf-base15,
yamt-lazymbuf-base14,
yamt-kmem-base3,
yamt-kmem-base2,
yamt-kmem-base,
yamt-kmem,
yamt-idlelwp-base8,
yamt-idlelwp,
wrstuden-revivesa-base-4,
wrstuden-revivesa-base-3,
wrstuden-revivesa-base-2,
wrstuden-revivesa-base-1,
wrstuden-revivesa-base,
wrstuden-revivesa,
wrstuden-fixsa-newbase,
wrstuden-fixsa-base-1,
wrstuden-fixsa-base,
wrstuden-fixsa,
vmlocking2-base3,
vmlocking2-base2,
vmlocking2-base1,
vmlocking2,
vmlocking-nbase,
vmlocking-base,
vmlocking,
uebayasi-xip-base4,
uebayasi-xip-base3,
uebayasi-xip-base2,
uebayasi-xip-base1,
uebayasi-xip-base,
uebayasi-xip,
tls-maxphys-base-20171202,
tls-maxphys-base,
tls-maxphys,
tls-earlyentropy-base,
tls-earlyentropy,
thorpej-atomic-base,
thorpej-atomic,
simonb-wapbl-nbase,
simonb-wapbl-base,
simonb-wapbl,
simonb-timecounters-base,
simonb-timecounters,
simonb-timcounters-final,
rpaulo-netinet-merge-pcb-base,
rpaulo-netinet-merge-pcb,
rmind-uvmplock-nbase,
rmind-uvmplock-base,
rmind-uvmplock,
rmind-smpnet-nbase,
rmind-smpnet-base,
rmind-smpnet,
riastradh-xf86-video-intel-2-7-1-pre-2-21-15,
riastradh-drm2-base3,
riastradh-drm2-base2,
riastradh-drm2-base1,
riastradh-drm2-base,
riastradh-drm2,
reinoud-bufcleanup-nbase,
reinoud-bufcleanup-base,
reinoud-bufcleanup,
prg-localcount2-base3,
prg-localcount2-base2,
prg-localcount2-base1,
prg-localcount2-base,
prg-localcount2,
post-newlock2-merge,
phil-wifi-base,
phil-wifi-20190609,
pgoyette-localcount-base,
pgoyette-localcount-20170426,
pgoyette-localcount-20170320,
pgoyette-localcount-20170107,
pgoyette-localcount-20161104,
pgoyette-localcount-20160806,
pgoyette-localcount-20160726,
pgoyette-localcount,
pgoyette-compat-merge-20190127,
pgoyette-compat-base,
pgoyette-compat-20190127,
pgoyette-compat-20190118,
pgoyette-compat-1226,
pgoyette-compat-1126,
pgoyette-compat-1020,
pgoyette-compat-0930,
pgoyette-compat-0906,
pgoyette-compat-0728,
pgoyette-compat-0625,
pgoyette-compat-0521,
pgoyette-compat-0502,
pgoyette-compat-0422,
pgoyette-compat-0415,
pgoyette-compat-0407,
pgoyette-compat-0330,
pgoyette-compat-0322,
pgoyette-compat-0315,
pgoyette-compat,
peter-altq-base,
peter-altq,
perseant-stdc-iso10646-base,
perseant-stdc-iso10646,
nick-nhusb-base-20170825,
nick-nhusb-base-20170204,
nick-nhusb-base-20161204,
nick-nhusb-base-20161004,
nick-nhusb-base-20160907,
nick-nhusb-base-20160529,
nick-nhusb-base-20160422,
nick-nhusb-base-20160319,
nick-nhusb-base-20151226,
nick-nhusb-base-20150921,
nick-nhusb-base-20150606,
nick-nhusb-base-20150406,
nick-nhusb-base,
nick-nhusb,
nick-net80211-sync-base,
nick-net80211-sync,
nick-hppapmap-base4,
nick-hppapmap-base3,
nick-hppapmap-base2,
nick-hppapmap-base,
nick-hppapmap,
nick-csl-alignment-base5,
nick-csl-alignment-base,
nick-csl-alignment,
newlock2-nbase,
newlock2-base,
newlock2,
netbsd-9-base,
netbsd-9-5-RELEASE,
netbsd-9-4-RELEASE,
netbsd-9-3-RELEASE,
netbsd-9-2-RELEASE,
netbsd-9-1-RELEASE,
netbsd-9-0-RELEASE,
netbsd-9-0-RC2,
netbsd-9-0-RC1,
netbsd-9,
netbsd-8-base,
netbsd-8-3-RELEASE,
netbsd-8-2-RELEASE,
netbsd-8-1-RELEASE,
netbsd-8-1-RC1,
netbsd-8-0-RELEASE,
netbsd-8-0-RC2,
netbsd-8-0-RC1,
netbsd-8,
netbsd-7-nhusb-base-20170116,
netbsd-7-nhusb-base,
netbsd-7-nhusb,
netbsd-7-base,
netbsd-7-2-RELEASE,
netbsd-7-1-RELEASE,
netbsd-7-1-RC2,
netbsd-7-1-RC1,
netbsd-7-1-2-RELEASE,
netbsd-7-1-1-RELEASE,
netbsd-7-1,
netbsd-7-0-RELEASE,
netbsd-7-0-RC3,
netbsd-7-0-RC2,
netbsd-7-0-RC1,
netbsd-7-0-2-RELEASE,
netbsd-7-0-1-RELEASE,
netbsd-7-0,
netbsd-7,
netbsd-6-base,
netbsd-6-1-RELEASE,
netbsd-6-1-RC4,
netbsd-6-1-RC3,
netbsd-6-1-RC2,
netbsd-6-1-RC1,
netbsd-6-1-5-RELEASE,
netbsd-6-1-4-RELEASE,
netbsd-6-1-3-RELEASE,
netbsd-6-1-2-RELEASE,
netbsd-6-1-1-RELEASE,
netbsd-6-1,
netbsd-6-0-RELEASE,
netbsd-6-0-RC2,
netbsd-6-0-RC1,
netbsd-6-0-6-RELEASE,
netbsd-6-0-5-RELEASE,
netbsd-6-0-4-RELEASE,
netbsd-6-0-3-RELEASE,
netbsd-6-0-2-RELEASE,
netbsd-6-0-1-RELEASE,
netbsd-6-0,
netbsd-6,
netbsd-5-base,
netbsd-5-2-RELEASE,
netbsd-5-2-RC1,
netbsd-5-2-3-RELEASE,
netbsd-5-2-2-RELEASE,
netbsd-5-2-1-RELEASE,
netbsd-5-2,
netbsd-5-1-RELEASE,
netbsd-5-1-RC4,
netbsd-5-1-RC3,
netbsd-5-1-RC2,
netbsd-5-1-RC1,
netbsd-5-1-5-RELEASE,
netbsd-5-1-4-RELEASE,
netbsd-5-1-3-RELEASE,
netbsd-5-1-2-RELEASE,
netbsd-5-1-1-RELEASE,
netbsd-5-1,
netbsd-5-0-RELEASE,
netbsd-5-0-RC4,
netbsd-5-0-RC3,
netbsd-5-0-RC2,
netbsd-5-0-RC1,
netbsd-5-0-2-RELEASE,
netbsd-5-0-1-RELEASE,
netbsd-5-0,
netbsd-5,
netbsd-4-base,
netbsd-4-0-RELEASE,
netbsd-4-0-RC5,
netbsd-4-0-RC4,
netbsd-4-0-RC3,
netbsd-4-0-RC2,
netbsd-4-0-RC1,
netbsd-4-0-1-RELEASE,
netbsd-4-0,
netbsd-4,
mjf-ufs-trans-base,
mjf-ufs-trans,
mjf-devfs2-base,
mjf-devfs2,
mjf-devfs-base,
mjf-devfs,
matt-premerge-20091211,
matt-nb8-mediatek-base,
matt-nb8-mediatek,
matt-nb6-plus-nbase,
matt-nb6-plus-base,
matt-nb6-plus,
matt-nb5-pq3-base,
matt-nb5-pq3,
matt-nb5-mips64-u2-k2-k4-k7-k8-k9,
matt-nb5-mips64-u1-k1-k5,
matt-nb5-mips64-premerge-20101231,
matt-nb5-mips64-premerge-20091211,
matt-nb5-mips64-k15,
matt-nb5-mips64,
matt-nb4-mips64-k7-u2a-k9b,
matt-nb4-arm-base,
matt-nb4-arm,
matt-mips64-premerge-20101231,
matt-mips64-base2,
matt-mips64-base,
matt-mips64,
matt-armv6-prevmlocking,
matt-armv6-nbase,
matt-armv6-base,
matt-armv6,
localcount-20160914,
khorben-n900,
keiichi-mipv6-nbase,
keiichi-mipv6-base,
keiichi-mipv6,
jymxensuspend-base,
jym-xensuspend-nbase,
jym-xensuspend-base,
jym-xensuspend,
jruoho-x86intr-base,
jruoho-x86intr,
jmcneill-usbmp-pre-base2,
jmcneill-usbmp-base9,
jmcneill-usbmp-base8,
jmcneill-usbmp-base7,
jmcneill-usbmp-base6,
jmcneill-usbmp-base5,
jmcneill-usbmp-base4,
jmcneill-usbmp-base3,
jmcneill-usbmp-base2,
jmcneill-usbmp-base10,
jmcneill-usbmp-base,
jmcneill-usbmp,
jmcneill-pm-base,
jmcneill-pm,
jmcneill-base,
jmcneill-audiomp3-base,
jmcneill-audiomp3,
jdolecek-ncqfixes-base,
jdolecek-ncqfixes,
jdolecek-ncq-base,
jdolecek-ncq,
isaki-audio2-base,
isaki-audio2,
hpcarm-cleanup-nbase,
hpcarm-cleanup-base,
hpcarm-cleanup,
haad-nbase2,
haad-dm-base2,
haad-dm-base1,
haad-dm-base,
haad-dm,
gdamore-uart-base,
gdamore-uart,
elad-kernelauth-base,
elad-kernelauth,
cube-autoconf-base,
cube-autoconf,
cherry-xenmp-base,
cherry-xenmp,
chap-midi-nbase,
chap-midi-base,
chap-midi,
bouyer-xeni386-nbase,
bouyer-xeni386-merge1,
bouyer-xeni386-base,
bouyer-xeni386,
bouyer-xenamd64-base2,
bouyer-xenamd64-base,
bouyer-xenamd64,
bouyer-socketcan-base1,
bouyer-socketcan-base,
bouyer-socketcan,
bouyer-quota2-nbase,
bouyer-quota2-base,
bouyer-quota2,
agc-symver-base,
agc-symver,
ad-socklock-base1,
ad-audiomp2-base,
ad-audiomp2,
ad-audiomp-base,
ad-audiomp,
abandoned-netbsd-4-base,
abandoned-netbsd-4
Branch point for: phil-wifi
Diff to: previous 1.19: preferred, colored
Changes since revision 1.19: +1 -1
lines
merge ktrace-lwp.
Revision 1.7.2.5: download - view: text, markup, annotated - select for diffs
Thu Nov 10 14:07:40 2005 UTC (21 years ago) by skrll
Branches: ktrace-lwp
Diff to: previous 1.7.2.4: preferred, colored; next MAIN 1.8: preferred, colored
Changes since revision 1.7.2.4: +7 -7
lines
Sync with HEAD. Here we go again...
Revision 1.18.2.1: download - view: text, markup, annotated - select for diffs
Fri Jun 17 13:35:50 2005 UTC (21 years, 5 months ago) by tron
Branches: netbsd-3
CVS tags: netbsd-3-1-RELEASE,
netbsd-3-1-RC4,
netbsd-3-1-RC3,
netbsd-3-1-RC2,
netbsd-3-1-RC1,
netbsd-3-1-1-RELEASE,
netbsd-3-1,
netbsd-3-0-RELEASE,
netbsd-3-0-RC6,
netbsd-3-0-RC5,
netbsd-3-0-RC4,
netbsd-3-0-RC3,
netbsd-3-0-RC2,
netbsd-3-0-RC1,
netbsd-3-0-3-RELEASE,
netbsd-3-0-2-RELEASE,
netbsd-3-0-1-RELEASE,
netbsd-3-0
Diff to: previous 1.18: preferred, colored; next MAIN 1.19: preferred, colored
Changes since revision 1.18: +7 -7
lines
Pull up revision 1.19 (requested by oster in ticket #472):
- avoid variable shadowing
- add a lot of const
- remove parameters from function declarations
Revision 1.19: download - view: text, markup, annotated - select for diffs
Sun May 29 22:03:09 2005 UTC (21 years, 5 months ago) by christos
Branches: MAIN
CVS tags: yamt-vop-base3,
yamt-vop-base2,
yamt-vop-base,
yamt-vop,
yamt-readahead-pervnode,
yamt-readahead-perfile,
yamt-readahead-base3,
yamt-readahead-base2,
yamt-readahead-base,
yamt-readahead,
yamt-lazymbuf,
thorpej-vnode-attr-base,
thorpej-vnode-attr,
ktrace-lwp-base
Diff to: previous 1.18: preferred, colored
Changes since revision 1.18: +7 -7
lines
- avoid variable shadowing
- add a lot of const
- remove parameters from functin declarations
Revision 1.17.4.1: download - view: text, markup, annotated - select for diffs
Fri Apr 29 11:29:15 2005 UTC (21 years, 6 months ago) by kent
Branches: kent-audio2
Diff to: previous 1.17: preferred, colored; next MAIN 1.18: preferred, colored
Changes since revision 1.17: +4 -4
lines
sync with -current
Revision 1.17.6.1: download - view: text, markup, annotated - select for diffs
Sat Mar 19 08:35:41 2005 UTC (21 years, 8 months ago) by yamt
Branches: yamt-km
Diff to: previous 1.17: preferred, colored; next MAIN 1.18: preferred, colored
Changes since revision 1.17: +4 -4
lines
sync with head. xen and whitespace. xen part is not finished.
Revision 1.7.2.4: download - view: text, markup, annotated - select for diffs
Fri Mar 4 16:50:06 2005 UTC (21 years, 8 months ago) by skrll
Branches: ktrace-lwp
Diff to: previous 1.7.2.3: preferred, colored
Changes since revision 1.7.2.3: +4 -4
lines
Sync with HEAD.
Hi Perry!
Revision 1.18: download - view: text, markup, annotated - select for diffs
Sun Feb 27 00:27:44 2005 UTC (21 years, 8 months ago) by perry
Branches: MAIN
CVS tags: yamt-km-base4,
yamt-km-base3,
netbsd-3-base,
kent-audio2-base
Branch point for: netbsd-3
Diff to: previous 1.17: preferred, colored
Changes since revision 1.17: +4 -4
lines
nuke trailing whitespace
Revision 1.7.2.3: download - view: text, markup, annotated - select for diffs
Tue Sep 21 13:32:52 2004 UTC (22 years, 1 month ago) by skrll
Branches: ktrace-lwp
Diff to: previous 1.7.2.2: preferred, colored
Changes since revision 1.7.2.2: +1 -1
lines
Fix the sync with head I botched.
Revision 1.7.2.2: download - view: text, markup, annotated - select for diffs
Sat Sep 18 14:50:54 2004 UTC (22 years, 2 months ago) by skrll
Branches: ktrace-lwp
Diff to: previous 1.7.2.1: preferred, colored
Changes since revision 1.7.2.1: +0 -0
lines
Sync with HEAD.
Revision 1.7.2.1: download - view: text, markup, annotated - select for diffs
Tue Aug 3 10:50:43 2004 UTC (22 years, 3 months ago) by skrll
Branches: ktrace-lwp
Diff to: previous 1.7: preferred, colored
Changes since revision 1.7: +53 -62
lines
Sync with HEAD
Revision 1.16.2.1: download - view: text, markup, annotated - select for diffs
Sun Apr 11 11:19:08 2004 UTC (22 years, 7 months ago) by tron
Branches: netbsd-2-0
CVS tags: netbsd-2-base,
netbsd-2-1-RELEASE,
netbsd-2-1-RC6,
netbsd-2-1-RC5,
netbsd-2-1-RC4,
netbsd-2-1-RC3,
netbsd-2-1-RC2,
netbsd-2-1-RC1,
netbsd-2-1,
netbsd-2-0-RELEASE,
netbsd-2-0-RC5,
netbsd-2-0-RC4,
netbsd-2-0-RC3,
netbsd-2-0-RC2,
netbsd-2-0-RC1,
netbsd-2-0-3-RELEASE,
netbsd-2-0-2-RELEASE,
netbsd-2-0-1-RELEASE,
netbsd-2
Diff to: previous 1.16: preferred, colored; next MAIN 1.17: preferred, colored
Changes since revision 1.16: +5 -4
lines
Pull up revision 1.17 (requested by oster in ticket #123):
These changes complete the effective removal of malloc() from all
write paths within RAIDframe. They also resolve the "panics with
RAID 5 sets with more than 3 components" issue which was present
(briefly) in the commits which were previously supposed to address
the malloc() issue.
With this new code the 5-component RAID 5 set panics are now gone.
It is also now also possible to swap to RAID 5.
The changes made are:
1) Introduce rf_AllocStripeBuffer() and rf_FreeStripeBuffer() to
allocate/free one stripe's worth of space. rf_AllocStripeBuffer() is
used in rf_MapUnaccessedPortionOfStripe() where it is not sufficient to
allocate memory using just rf_AllocBuffer(). rf_FreeStripeBuffer() is
called from rf_FreeRaidAccDesc(), well after the DAG is finished.
2) Add a set of emergency "stripe buffers" to struct RF_Raid_s.
Arrange for their initialization in rf_Configure(). In low-memory
situations these buffers will be returned by rf_AllocStripeBuffer()
and re-populated by rf_FreeStripeBuffer().
3) Move RF_VoidPointerListElem_t *iobufs from the dagHeader into
into struct RF_RaidAccessDesc_s. This is more consistent with the
original code, and will not result in items being freed "too early".
4) Add a RF_RaidAccessDesc_t *desc to RF_DagHeader_s so that we have a
way to find desc->iobufs.
5) Arrange for desc in the DagHeader to be initialized in InitHdrNode().
6) Don't cleanup iobufs in rf_FreeDAG() -- the freeing is now delayed
until rf_FreeRaidAccDesc() (which is how the original code handled the
allocList, and for which there seem to be some subtle, undocumented
assumptions).
7) Rename rf_AllocBuffer2() to be rf_AllocBuffer() and remove the
former rf_AllocBuffer(). Fix all callers of rf_AllocBuffer().
(This was how it was *supposed* to be after the last time these
changes were made, before they were backed out).
8) Remove RF_IOBufHeader and all references to it.
9) Remove desc->cleanupList and all references to it.
Fixes PR#20191
Revision 1.17: download - view: text, markup, annotated - select for diffs
Fri Apr 9 23:10:16 2004 UTC (22 years, 7 months ago) by oster
Branches: MAIN
CVS tags: yamt-km-base2,
yamt-km-base,
kent-audio1-beforemerge,
kent-audio1-base,
kent-audio1
Branch point for: yamt-km,
kent-audio2
Diff to: previous 1.16: preferred, colored
Changes since revision 1.16: +5 -4
lines
These changes complete the effective removal of malloc() from all
write paths within RAIDframe. They also resolve the "panics with
RAID 5 sets with more than 3 components" issue which was present
(briefly) in the commits which were previously supposed to address
the malloc() issue.
With this new code the 5-component RAID 5 set panics are now gone.
It is also now also possible to swap to RAID 5.
The changes made are:
1) Introduce rf_AllocStripeBuffer() and rf_FreeStripeBuffer() to
allocate/free one stripe's worth of space. rf_AllocStripeBuffer() is
used in rf_MapUnaccessedPortionOfStripe() where it is not sufficient to
allocate memory using just rf_AllocBuffer(). rf_FreeStripeBuffer() is
called from rf_FreeRaidAccDesc(), well after the DAG is finished.
2) Add a set of emergency "stripe buffers" to struct RF_Raid_s.
Arrange for their initialization in rf_Configure(). In low-memory
situations these buffers will be returned by rf_AllocStripeBuffer()
and re-populated by rf_FreeStripeBuffer().
3) Move RF_VoidPointerListElem_t *iobufs from the dagHeader into
into struct RF_RaidAccessDesc_s. This is more consistent with the
original code, and will not result in items being freed "too early".
4) Add a RF_RaidAccessDesc_t *desc to RF_DagHeader_s so that we have a
way to find desc->iobufs.
5) Arrange for desc in the DagHeader to be initialized in InitHdrNode().
6) Don't cleanup iobufs in rf_FreeDAG() -- the freeing is now delayed
until rf_FreeRaidAccDesc() (which is how the original code handled the
allocList, and for which there seem to be some subtle, undocumented
assumptions).
7) Rename rf_AllocBuffer2() to be rf_AllocBuffer() and remove the
former rf_AllocBuffer(). Fix all callers of rf_AllocBuffer().
(This was how it was *supposed* to be after the last time these
changes were made, before they were backed out).
8) Remove RF_IOBufHeader and all references to it.
9) Remove desc->cleanupList and all references to it.
Fixes PR#20191
Revision 1.16: download - view: text, markup, annotated - select for diffs
Tue Mar 23 21:53:36 2004 UTC (22 years, 7 months ago) by oster
Branches: MAIN
CVS tags: netbsd-2-0-base
Branch point for: netbsd-2-0
Diff to: previous 1.15: preferred, colored
Changes since revision 1.15: +3 -2
lines
Partially back out some changes that were causing grief with
RAID5 sets with more than 3 drives. Still need to figure out why
the original changes were losing, but need the version in tree reliable
first!
Huge THANKS to Juergen Hannken-Illjes for helping track down
the changes that were causing the lossage.
Revision 1.15: download - view: text, markup, annotated - select for diffs
Sat Mar 20 16:48:05 2004 UTC (22 years, 8 months ago) by oster
Branches: MAIN
Diff to: previous 1.14: preferred, colored
Changes since revision 1.14: +33 -61
lines
Cleanup function prototypes.
Revision 1.14: download - view: text, markup, annotated - select for diffs
Sat Mar 20 15:56:21 2004 UTC (22 years, 8 months ago) by oster
Branches: MAIN
Diff to: previous 1.13: preferred, colored
Changes since revision 1.13: +2 -6
lines
[bah.. specifying rf_dagutils.c twice on a checkin doesn't get you
rf_dagutils.h... missed this one from yesterday. sorry folks :( ]
Change signature of rf_AllocBuffer() to take a dag_h and buffer size
instead of an PDA and an alloclist. This lets us do the vple dance
inside of rf_AllocBuffer().
Cleanup usage of rf_AllocIOBuffer() and use rf_AllocBuffer() instead.
Fix all uses of rf_AllocBuffer() to conform to the new way of doing
things.
Revision 1.13: download - view: text, markup, annotated - select for diffs
Sat Mar 20 04:22:05 2004 UTC (22 years, 8 months ago) by oster
Branches: MAIN
Diff to: previous 1.12: preferred, colored
Changes since revision 1.12: +5 -1
lines
For each RAID set, pre-allocate a number of "emergency buffers" to be
used in the event that we can't malloc a buffer of the appropriate
size in the traditional way. rf_AllocIOBuffer() and rf_FreeIOBuffer()
deal with allocating/freeing these structures. These buffers are
stored in a list on the 'iobuf' list. iobuf_count keeps track of how
many buffers are available, and numEmergencyBuffers is the effective
"high-water" mark for the freelist. The buffers allocated by
rf_AllocIOBuffer() are stripe-unit sized, which is the maximum
size requested by any of the callers.
Add an iobufs entry to RF_DagHeader_s. Use it for keeping track of
buffers that get allocated from the free-list.
Add a "generic list" pool (VoidPointerListElement Pool) for elements
used to maintain a list of allocated memory. [It is somewhat less
than ideal to add another little pool to handle this...]
Teach rf_AllocBuffer() to use the new rf_AllocIOBuffer(). Modify
other Mallocs to use rf_AllocIOBuffer(), and to update dag_h->iobufs as
appropriate.
Update rf_FreeDAG() to handle cleanup of dag_h->iobufs.
While here, add some missing pool_destroy() calls for a number of pools.
With these changes, it should (in theory) be possible to swap on
RAID 5 sets again. That said, I've not had any success there yet --
but the last issue I saw at least wasn't in RAIDframe. :-}
[There is room for this code to become a bit more consise, but I
wanted to do a checkpoint here with something known to work :) ]
Revision 1.12: download - view: text, markup, annotated - select for diffs
Fri Mar 19 17:01:26 2004 UTC (22 years, 8 months ago) by oster
Branches: MAIN
Diff to: previous 1.11: preferred, colored
Changes since revision 1.11: +4 -1
lines
Introduce a dual-purpose pool for providing pointer and param "caches"
for RF_DagNode_t's. Scale the structure size based on RF_MAXCOL.
Use the new allocation method in InitNode(). Note that we can't get
rid of the mallocs in there until we can prove that this new
allocation method is a strict upper bound. Unless someone tries
running a RAID set with 40 components, the mallocs here shouldn't
shouldn't be an issue. (and if someone does make a set with 40 components
they will run into other issues with other constants long before
then)
Revision 1.11: download - view: text, markup, annotated - select for diffs
Thu Mar 18 16:40:05 2004 UTC (22 years, 8 months ago) by oster
Branches: MAIN
Diff to: previous 1.10: preferred, colored
Changes since revision 1.10: +4 -1
lines
- Introduce a 'dagnode' pool. Initialize it and allow for cleanup.
Provide rf_AllocDAGNode() and rf_FreeDAGNode() to handle
allocation/freeing.
- Introduce a "nodes" linked list of RF_DagNode_t's into the DAG header.
Initialize nodes in InitHdrNode(). Arrange for nodes cleanup in rf_FreeDAG().
- Add a "list_next" to RF_DagNode_t to keep track of nodes on the
above "nodes" list. (This is distinct from the "next" field of
RF_DagNode_t, which keeps track of the firing order of nodes.)
"list_next" gets used in the cleanup routines, and in traversing
through a set of nodes that belong to a particular set of nodes
(e.g. those belonging to xorNodes for a given DAG).
- use rf_AllocDAGNode() instead of mallocs of variable-sized arrays of
RF_DagNode_t's. Mostly mechanical changes to convert the DAG construction
from "access nodes via an array index" to "access nodes via a 'nextnode'
pointer".
- rework a couple of tricky spots where assumptions about the node order
was being abused.
- performance remains consistent with performance before these changes.
[Thanks to Simon Burge (simonb at you.know.where) for looking over
the mechanical changes to make sure I didn't biff anything.]
Revision 1.10: download - view: text, markup, annotated - select for diffs
Sat Mar 6 23:52:20 2004 UTC (22 years, 8 months ago) by oster
Branches: MAIN
Diff to: previous 1.9: preferred, colored
Changes since revision 1.9: +2 -2
lines
rf_AllocBuffer() doesn't do anything with its dag_h parameter. Nuke
it, and adjust callers.
Revision 1.9: download - view: text, markup, annotated - select for diffs
Sun Feb 29 01:24:34 2004 UTC (22 years, 8 months ago) by oster
Branches: MAIN
Diff to: previous 1.8: preferred, colored
Changes since revision 1.8: +9 -1
lines
Stripe functions are now handled by a linked-list instead of a
runtime-variable array.
Fix a bug where stripeFuncs was being freed, and then being used after
(in the case of numStripesBailed > 0).
Revision 1.8: download - view: text, markup, annotated - select for diffs
Fri Feb 27 02:55:17 2004 UTC (22 years, 8 months ago) by oster
Branches: MAIN
Diff to: previous 1.7: preferred, colored
Changes since revision 1.7: +4 -1
lines
Use a dynamically allocated linked list of dagLists instead of using a
dynamically allocated variable-sized array (dagArray). Convert code
to use the new linked list stuff instead of the array stuff (the ratio
of one dagList per stripe still applies). The big advantage is in
being able to more efficiently allocate the dagLists on-the-fly, and
not have to know the size(s) of the array beforehand.
Revision 1.7: download - view: text, markup, annotated - select for diffs
Sun Feb 9 10:04:33 2003 UTC (23 years, 9 months ago) by jdolecek
Branches: MAIN
Branch point for: ktrace-lwp
Diff to: previous 1.6: preferred, colored
Changes since revision 1.6: +3 -3
lines
constify some
Revision 1.3.20.2: download - view: text, markup, annotated - select for diffs
Fri Oct 18 02:43:45 2002 UTC (24 years, 1 month ago) by nathanw
Branches: nathanw_sa
CVS tags: nathanw_sa_end
Diff to: previous 1.3.20.1: preferred, colored; branchpoint 1.3: preferred, colored; next MAIN 1.4: preferred, colored
Changes since revision 1.3.20.1: +51 -43
lines
Catch up to -current.
Revision 1.3.22.2: download - view: text, markup, annotated - select for diffs
Thu Oct 10 18:41:46 2002 UTC (24 years, 1 month ago) by jdolecek
Branches: kqueue
Diff to: previous 1.3.22.1: preferred, colored; branchpoint 1.3: preferred, colored; next MAIN 1.4: preferred, colored
Changes since revision 1.3.22.1: +51 -43
lines
sync kqueue with -current; this includes merge of gehenna-devsw branch,
merge of i386 MP branch, and part of autoconf rototil work
Revision 1.6: download - view: text, markup, annotated - select for diffs
Sat Sep 21 14:47:07 2002 UTC (24 years, 2 months ago) by oster
Branches: MAIN
CVS tags: nathanw_sa_before_merge,
nathanw_sa_base,
kqueue-beforemerge,
kqueue-base,
kqueue-aftermerge,
gmcgarry_ucred_base,
gmcgarry_ucred,
gmcgarry_ctxsw_base,
gmcgarry_ctxsw,
fvdl_fs64_base
Diff to: previous 1.5: preferred, colored
Changes since revision 1.5: +51 -40
lines
Minor cleanup/reformatting.
Revision 1.5: download - view: text, markup, annotated - select for diffs
Sat Sep 21 00:56:57 2002 UTC (24 years, 2 months ago) by oster
Branches: MAIN
Diff to: previous 1.4: preferred, colored
Changes since revision 1.4: +1 -4
lines
rf_MakePropListEntry isn't used anywhere, so nuke it. Thanks Krister!
Revision 1.3.22.1: download - view: text, markup, annotated - select for diffs
Thu Jan 10 19:57:41 2002 UTC (24 years, 10 months ago) by thorpej
Branches: kqueue
Diff to: previous 1.3: preferred, colored
Changes since revision 1.3: +3 -2
lines
Sync kqueue branch with -current.
Revision 1.3.20.1: download - view: text, markup, annotated - select for diffs
Mon Oct 22 20:41:34 2001 UTC (25 years ago) by nathanw
Branches: nathanw_sa
Diff to: previous 1.3: preferred, colored
Changes since revision 1.3: +3 -2
lines
Catch up to -current.
Revision 1.3.24.1: download - view: text, markup, annotated - select for diffs
Thu Oct 11 00:02:17 2001 UTC (25 years, 1 month ago) by fvdl
Branches: thorpej-devvp
Diff to: previous 1.3: preferred, colored; next MAIN 1.4: preferred, colored
Changes since revision 1.3: +3 -2
lines
Catch up with -current. Fix some bogons in the sparc64 kbd/ms
attach code. cd18xx conversion provided by mrg.
Revision 1.4: download - view: text, markup, annotated - select for diffs
Thu Oct 4 15:58:52 2001 UTC (25 years, 1 month ago) by oster
Branches: MAIN
CVS tags: thorpej-mips-cache-base,
thorpej-mips-cache,
thorpej-devvp-base3,
newlock-base,
newlock,
netbsd-1-6-base,
netbsd-1-6-RELEASE,
netbsd-1-6-RC3,
netbsd-1-6-RC2,
netbsd-1-6-RC1,
netbsd-1-6-PATCH002-RELEASE,
netbsd-1-6-PATCH002-RC4,
netbsd-1-6-PATCH002-RC3,
netbsd-1-6-PATCH002-RC2,
netbsd-1-6-PATCH002-RC1,
netbsd-1-6-PATCH002,
netbsd-1-6-PATCH001-RELEASE,
netbsd-1-6-PATCH001-RC3,
netbsd-1-6-PATCH001-RC2,
netbsd-1-6-PATCH001-RC1,
netbsd-1-6-PATCH001,
netbsd-1-6,
ifpoll-base,
gehenna-devsw-base,
gehenna-devsw,
eeh-devprop-base,
eeh-devprop
Diff to: previous 1.3: preferred, colored
Changes since revision 1.3: +3 -2
lines
Step 2 of the disentanglement. We now look to <dev/raidframe/*> for
the stuff that used to live in rf_types.h, rf_raidframe.h, rf_layout.h,
rf_netbsd.h, rf_raid.h, rf_decluster,h, and a few other places.
Believe it or not, when this is all done, things will be cleaner.
No functional changes to RAIDframe.
Revision 1.3: download - view: text, markup, annotated - select for diffs
Fri Feb 5 00:06:08 1999 UTC (27 years, 9 months ago) by oster
Branches: MAIN
CVS tags: wrstuden-devbsize-base,
wrstuden-devbsize-19991221,
wrstuden-devbsize,
thorpej_scsipi_nbase,
thorpej_scsipi_beforemerge,
thorpej_scsipi_base,
thorpej_scsipi,
thorpej-devvp-base2,
thorpej-devvp-base,
pre-chs-ubcperf,
post-chs-ubcperf,
netbsd-1-5-base,
netbsd-1-5-RELEASE,
netbsd-1-5-PATCH003,
netbsd-1-5-PATCH002,
netbsd-1-5-PATCH001,
netbsd-1-5-BETA2,
netbsd-1-5-BETA,
netbsd-1-5-ALPHA2,
netbsd-1-5,
netbsd-1-4-base,
netbsd-1-4-RELEASE,
netbsd-1-4-PATCH003,
netbsd-1-4-PATCH002,
netbsd-1-4-PATCH001,
netbsd-1-4,
minoura-xpg4dl-base,
minoura-xpg4dl,
kame_14_19990705,
kame_14_19990628,
kame_141_19991130,
kame,
fvdl-softdep-base,
fvdl-softdep,
comdex-fall-1999-base,
comdex-fall-1999,
chs-ubc2-newbase,
chs-ubc2-base,
chs-ubc2
Branch point for: thorpej-devvp,
nathanw_sa,
kqueue
Diff to: previous 1.2: preferred, colored
Changes since revision 1.2: +48 -47
lines
Phase 2 of the RAIDframe cleanup. The source is now closer to KNF
and is much easier to read. No functionality changes.
Revision 1.2: download - view: text, markup, annotated - select for diffs
Tue Jan 26 02:33:54 1999 UTC (27 years, 9 months ago) by oster
Branches: MAIN
Diff to: previous 1.1: preferred, colored
Changes since revision 1.1: +1 -73
lines
RAIDframe cleanup, phase 1. Nuke simulator support, user-land driver,
out-dated comments, and other unneeded stuff. This helps prepare
for cleaning up the rest of the code, and adding new functionality.
No functional changes to the kernel code in this commit.
Revision 1.1: download - view: text, markup, annotated - select for diffs
Fri Nov 13 04:20:28 1998 UTC (28 years ago) by oster
Branches: MAIN
CVS tags: kenh-if-detach-base,
kenh-if-detach
RAIDframe, version 1.1, from the Parallel Data Laboratory at
Carnegie Mellon University. Full RAID implementation, including
levels 0, 1, 4, 5, 6, parity logging, and a few other goodies.
Ported to NetBSD by Greg Oster.
CVSweb <webmaster@jp.NetBSD.org>