1 ## Note: this is my personal todo and ideas list (alexh@)
4 - Improve to support external scripts/programs providing passphrases
8 - separate out common arch parts (linprocfs, for example)
12 * Fix the crash analysis script (or rather the programs it calls)
16 * Take a look at updating lvm/dm/libdm
19 o Added VT6105M specific register definitions. VT6105M has the
20 following hardware capabilities.
21 - Tx/Rx IP/TCP/UDP checksum offload.
22 - VLAN hardware tag insertion/extraction. Due to lack of information
23 for getting extracted VLAN tag in Rx path, VLAN hardware support
24 was not implemented yet.
25 - CAM(Content Addressable Memory) based 32 entry perfect multicast/
28 o Implemented CAM based 32 entry perfect multicast filtering for
29 VT6105M. If number of multicast entry is greater than 32, vr(4)
30 uses traditional hash based filtering.
32 * rip out the disk partitioning from the disk subsystem and implement it in a more general fashion
33 - crazy idea: as dm targets with an auto-configuration option!
35 * sync some more opencrypto from OpenBSD
37 * ATA (automatic) spindown (see FreeBSD current)
40 http://svn.freebsd.org/viewvc/base?view=revision&revision=127969
44 - some incorrect accounting going on, don't remember details :)
47 - make it work without whiteout
54 * RedZone, a buffer corruption protection for the kernel malloc(9) facility has been implemented.
55 - This detects both buffer underflows and overflows at runtime on free(9) and realloc(9),
56 and prints backtraces from where memory was allocated and from where it was freed.
59 * port uart driver (?)
61 * port wscons (?) or update syscons
62 - probably way too much effort (wscons)
66 - wrapper is included for userland; should be easy to port
67 - http://svn.freebsd.org/viewvc/base?view=revision&revision=184610
68 - http://turbocat.net/~hselasky/usb4bsd/
69 - http://gitweb.dragonflybsd.org/~polachok/dragonfly.git/shortlog/refs/heads/usb2
71 * suspend/resume for SMP x86
72 - http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004879.html
74 * AMD64 suspend/resume
75 - http://svn.freebsd.org/viewvc/base?view=revision&revision=189903
82 [alexh@leaf:~/home] $ roundup-server -p 8080 bt=bugtracker
85 -05:48- : dillon@: no, double frees to the object cache are nasty. It can't detect them. the object
86 winds up in the magazine array twice
87 -05:48- : dillon@: (and possibly different magazines, too)
88 -05:49- : alexh@: can't I just write some magic to a free object on the first objcache_put and check
89 if it's there on objcache_put?
90 -05:49- : alexh@: and clear it on objcache_get, anyways
91 -05:50- : dillon@: no, because the object is still may have live-initialized fields
92 -05:50- : dillon@: because it hasn't been dtor'ed yet (one of the features of the objcache, to avoid
93 having to reinitialize objects every time)
94 -05:50- : dillon@: the mbuf code uses that feature I think, probably other bits too
95 -05:51- : dillon@: theoretically we could allocate slightly larger objects and store a magic number at
96 offset [-1] or something like that, but it gets a little iffy doing that
97 -05:52- : dillon@: the objcache with the objcache malloc default could probably do something like that
99 -05:52- : dillon@: I don't consider memory tracking to be a huge issue w/ dragonfly, though I like the
100 idea of being able to do it. It is a much bigger problem in FreeBSD due to the
101 large number of committers
104 -05:55- : dillon@: For the slab allocator you may be able to do something using the Zone header.
105 -05:55- : dillon@: the slab allocator in fact I think already has optional code to allocate a tracking
106 bitmap to detect double-frees
107 -05:56- : dillon@: sorry, I just remembered the bit about the power-of-2 allocations
108 -05:56- : dillon@: for example, power-of-2-sized allocations are guaranteed not only to be aligned on
109 that particular size boundary, but also to not cross a PAGE_BOUNDARY (unless the
111 -05:57- : dillon@: various subsystems such as AHCI depend on that behavior to allocate system
112 structures for which the chipsets only allow one DMA descriptor.
113 -05:59- : alexh@: http://svn.freebsd.org/viewvc/base/head/sys/vm/redzone.c?view=markup&pathrev=155086
114 < this is redzone. it basically calls redzone_addr_ntor() to increase the size in
115 malloc(), and then redzone_setup() just before returning the chunk
116 -06:02- : dillon@: jeeze. that looks horrible.
117 -06:03- : alexh@: I don't quite get that nsize + redzone_roundup(nsize)
118 -06:03- : dillon@: I don't get it either. It would completely break power-of-2-sized alignments in the
120 -06:04- : dillon@: hmmm. well, no it won't break them, but the results are oging to be weird
121 -06:04- : dillon@: ick.
123 -06:15- : dillon@: if the original request is a power of 2 the redzone adjusted request must be a power
125 -06:15- : dillon@: basically
126 -06:16- : dillon@: so original request 64, redzone request must be 128, 256, 512, 1024, etc.
127 -06:16- : alexh@: yah, k
128 -06:16- : dillon@: original request 32, current redzone code would be 32+128 which is WRONG.
129 -06:16- : alexh@: how big is PAGE_SIZE ?
130 -06:16- : dillon@: 4096 on i386 and amd64
131 -06:17- : alexh@: and one single malloc can't be bigger than that?
132 -06:17- : dillon@: I'm fairly sure our kmalloc does not guarantee alignment past PAGE_SIZE (that is,
133 the alignment will be only PAGE_SIZE eve if you allocate PAGE_SIZE*2)
134 -06:17- : dillon@: a single kmalloc can be larger then PAGE_SIZe
135 -06:18- : dillon@: it will use the zone up to around 1/2 the zone size (~64KB I think), after which it
136 allocates pages directly with the kernel kvm allocator
137 -06:18- : dillon@: if you look at the kmalloc code you will see the check for oversized allocations
138 -06:18- : alexh@: yah, saw that
139 -06:18- : alexh@: "handle large allocations directly"
140 -06:19- : alexh@: not sure how to do this, really, as the size is obviously also changed in
142 -06:20- : alexh@: but kmem_slab_alloc isn't called always, is it?
143 -06:20- : alexh@: only if the req doesn't fit into an existant zone
144 -06:20- : dillon@: right
145 -06:20- : dillon@: you don't want to redzone the zone allocation itself