[haiku-development] Re: Odd area allocation patterns by some kernel drivers
- From: "Rene Gollent" <anevilyak@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sat, 8 Mar 2008 08:46:08 -0600
> Well, in BSD it's certainly intentional. For Haiku, it's currently not
Would you mind elaborating as to why? :) I'm just wondering.
> so nice, as the area management doesn't use the best possible
> algorithms (besides needing a bit of memory for each area, but that
> applies to both platforms).
> I think for Firewire there is even an open bug report for this
> behaviour, I didn't know the nforce driver was doing something similar.
> I guess no one would mind if you'd fix that :-))
>
I can try :)
Regards,
Rene
- Follow-Ups:
- References:
- [haiku-development] Odd area allocation patterns by some kernel drivers
- From: Rene Gollent
- [haiku-development] Re: Odd area allocation patterns by some kernel drivers
- From: Axel Dörfler
Other related posts:
- » [haiku-development] Odd area allocation patterns by some kernel drivers
- » [haiku-development] Re: Odd area allocation patterns by some kernel drivers
- » [haiku-development] Re: Odd area allocation patterns by some kernel drivers
- » [haiku-development] Re: Odd area allocation patterns by some kernel drivers
- [haiku-development] Odd area allocation patterns by some kernel drivers
- From: Rene Gollent
- [haiku-development] Re: Odd area allocation patterns by some kernel drivers
- From: Axel Dörfler