Re: separating out memory checks from INVARIANTS
- From: Jeff Roberson <jroberson@xxxxxxxxxxxxxx>
- Date: Sat, 15 Mar 2008 19:54:29 -1000 (HST)
On Sat, 15 Mar 2008, Kip Macy wrote:
I find that the serialization of memory allocation frequently hides
race conditions. I would like to, at the very least, add an option to
disable the memory checks if not make the memory checks a completely
separate option. My knee jerk reaction to avoiding bikesheds is to
simply add it to my own tree and forget about it. However, this has
come up often enough that I feel that it warrants consideration.
Thoughts?
One other option that I have frequently considered is to convert UMA from using an array of bytes to using bitfields to represent the free space in a slab. Then you could use atomics to update the required information. It'd be a bit of work. Maybe a good SoC? :)
Jeff
_______________________________________________
-Kip
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: separating out memory checks from INVARIANTS
- From: Kip Macy
- Re: separating out memory checks from INVARIANTS
- References:
- separating out memory checks from INVARIANTS
- From: Kip Macy
- separating out memory checks from INVARIANTS
- Prev by Date: separating out memory checks from INVARIANTS
- Next by Date: Re: [PATCH] hwpmc(4) changes to use 'mp_maxid' instead of 'mp_ncpus'.
- Previous by thread: separating out memory checks from INVARIANTS
- Next by thread: Re: separating out memory checks from INVARIANTS
- Index(es):
Relevant Pages
|
