1 ## Note: this is my personal todo and ideas list (alexh@)
3 * add a non-persistent unionfs VFS
4 - while this does not fully replace unionfs, it would deal with a few of the situations where unionfs is useful
5 - additionally the complexity is much lower, since everything can be kept in memory
7 * bring the samba3 hammer shadow copy foo to maturity
9 * add a communication channel mechanism to dm
10 - essentially a way to send messages and receive responses to dm target instances
12 * add serpent and twofish xts modes to opencrypto
14 * add serpent and twofish support to dm_target_crypt
16 * Add TrueCrypt support
17 - Simply add a userland tool that sets dm_target_crypt up with the right parameters, extracted from the TrueCrypt header
18 - https://github.com/bwalex/tc-play <- done!
19 - needs OpenSSL with XTS support; probably next major release
20 - add Serpent and Twofish support to tc-play
21 - add cascaded cipher support to tc-play ?
25 * Keep opencrypto up-to-date
26 - http://www.openbsd.org/cgi-bin/cvsweb/src/sys/crypto/
28 * Port hwpmc & dig into (boot-up) performance
32 - separate out common arch parts (linprocfs, for example)
34 * Fix the crash analysis script (or rather the programs it calls [some segfault])
36 * Take a look at updating lvm/dm/libdevicemapper
38 * Take a look at importing libdm from NetBSD
39 - would allow tc-play and similarly newly developed foo to avoid GPL license issues
41 * rip out the disk partitioning from the disk subsystem and implement it in a more general fashion
42 - crazy idea: as dm targets with an auto-configuration option!
43 - would require to be able to create dm targets with an arbitrary name and not in /dev/mapper
45 * ATA (automatic) spindown (see FreeBSD current)
48 http://svn.freebsd.org/viewvc/base?view=revision&revision=127969
52 - some incorrect accounting going on, don't remember details :)
55 - make it work without whiteout
61 * Fix ipsec, get rid of old ipsec
64 - Added VT6105M specific register definitions. VT6105M has the following hardware capabilities.
65 - Tx/Rx IP/TCP/UDP checksum offload.
66 - VLAN hardware tag insertion/extraction. Due to lack of information
67 for getting extracted VLAN tag in Rx path, VLAN hardware support
68 was not implemented yet.
69 - CAM(Content Addressable Memory) based 32 entry perfect multicast/
72 o Implemented CAM based 32 entry perfect multicast filtering for
73 VT6105M. If number of multicast entry is greater than 32, vr(4)
74 uses traditional hash based filtering.
76 * RedZone, a buffer corruption protection for the kernel malloc(9) facility has been implemented.
77 - This detects both buffer underflows and overflows at runtime on free(9) and realloc(9),
78 and prints backtraces from where memory was allocated and from where it was freed.
81 * port uart driver (?)
83 * port wscons (?) or update syscons
84 - probably way too much effort (wscons)
88 - wrapper is included for userland; should be easy to port
89 - http://svn.freebsd.org/viewvc/base?view=revision&revision=184610
90 - http://turbocat.net/~hselasky/usb4bsd/
91 - http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/shortlog/refs/heads/usb2
93 * suspend/resume for SMP x86
94 - http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html
96 * AMD64 suspend/resume
97 - http://svn.freebsd.org/viewvc/base?view=revision&revision=189903
104 [alexh@leaf:~/home] $ roundup-server -p 8080 bt=bugtracker
107 -05:48- : dillon@: no, double frees to the object cache are nasty. It can't detect them. the object
108 winds up in the magazine array twice
109 -05:48- : dillon@: (and possibly different magazines, too)
110 -05:49- : alexh@: can't I just write some magic to a free object on the first objcache_put and check
111 if it's there on objcache_put?
112 -05:49- : alexh@: and clear it on objcache_get, anyways
113 -05:50- : dillon@: no, because the object is still may have live-initialized fields
114 -05:50- : dillon@: because it hasn't been dtor'ed yet (one of the features of the objcache, to avoid
115 having to reinitialize objects every time)
116 -05:50- : dillon@: the mbuf code uses that feature I think, probably other bits too
117 -05:51- : dillon@: theoretically we could allocate slightly larger objects and store a magic number at
118 offset [-1] or something like that, but it gets a little iffy doing that
119 -05:52- : dillon@: the objcache with the objcache malloc default could probably do something like that
121 -05:52- : dillon@: I don't consider memory tracking to be a huge issue w/ dragonfly, though I like the
122 idea of being able to do it. It is a much bigger problem in FreeBSD due to the
123 large number of committers
126 -05:55- : dillon@: For the slab allocator you may be able to do something using the Zone header.
127 -05:55- : dillon@: the slab allocator in fact I think already has optional code to allocate a tracking
128 bitmap to detect double-frees
129 -05:56- : dillon@: sorry, I just remembered the bit about the power-of-2 allocations
130 -05:56- : dillon@: for example, power-of-2-sized allocations are guaranteed not only to be aligned on
131 that particular size boundary, but also to not cross a PAGE_BOUNDARY (unless the
133 -05:57- : dillon@: various subsystems such as AHCI depend on that behavior to allocate system
134 structures for which the chipsets only allow one DMA descriptor.
135 -05:59- : alexh@: http://svn.freebsd.org/viewvc/base/head/sys/vm/redzone.c?view=markup&pathrev=155086
136 < this is redzone. it basically calls redzone_addr_ntor() to increase the size in
137 malloc(), and then redzone_setup() just before returning the chunk
138 -06:02- : dillon@: jeeze. that looks horrible.
139 -06:03- : alexh@: I don't quite get that nsize + redzone_roundup(nsize)
140 -06:03- : dillon@: I don't get it either. It would completely break power-of-2-sized alignments in the
142 -06:04- : dillon@: hmmm. well, no it won't break them, but the results are oging to be weird
143 -06:04- : dillon@: ick.
145 -06:15- : dillon@: if the original request is a power of 2 the redzone adjusted request must be a power
147 -06:15- : dillon@: basically
148 -06:16- : dillon@: so original request 64, redzone request must be 128, 256, 512, 1024, etc.
149 -06:16- : alexh@: yah, k
150 -06:16- : dillon@: original request 32, current redzone code would be 32+128 which is WRONG.
151 -06:16- : alexh@: how big is PAGE_SIZE ?
152 -06:16- : dillon@: 4096 on i386 and amd64
153 -06:17- : alexh@: and one single malloc can't be bigger than that?
154 -06:17- : dillon@: I'm fairly sure our kmalloc does not guarantee alignment past PAGE_SIZE (that is,
155 the alignment will be only PAGE_SIZE eve if you allocate PAGE_SIZE*2)
156 -06:17- : dillon@: a single kmalloc can be larger then PAGE_SIZe
157 -06:18- : dillon@: it will use the zone up to around 1/2 the zone size (~64KB I think), after which it
158 allocates pages directly with the kernel kvm allocator
159 -06:18- : dillon@: if you look at the kmalloc code you will see the check for oversized allocations
160 -06:18- : alexh@: yah, saw that
161 -06:18- : alexh@: "handle large allocations directly"
162 -06:19- : alexh@: not sure how to do this, really, as the size is obviously also changed in
164 -06:20- : alexh@: but kmem_slab_alloc isn't called always, is it?
165 -06:20- : alexh@: only if the req doesn't fit into an existant zone
166 -06:20- : dillon@: right
167 -06:20- : dillon@: you don't want to redzone the zone allocation itself