Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Darwin disk I/O - better interactive response

>> Even if I held that position, it would be wrong of me to assume that
>> everyone else uses computers the same way I do.
>
>Good. Then you might agree that some of us don't want to use Darwin as
>merely a server or merely a BSD variant, but would like to see it DEVELOP
>into a more Mac like PERSONAL computer OS...


You guys are drifting waaaaay off into meta-arguments.

Might I suggest that you agree do disagree (or at least misunderstand each other?)

If you have a specific change that you think should be made to darwin, we can discuss that.

We talked about ordering the write que, and it was mentioned that this would be counterproductive, since the device firmware now does this for us.

We can talk about fine tuning the scheduler, but this is something that people spend months on, using as much real world data as possible, and it's still a black art, capable of causing all sorts of priority inversion problems. It's a subject best left lightly discussed unless you have a *specific* change that you want to make, and then you'd better be prepared to defend your changes.

You have the code. If one has a point to prove, then one should prove it.

As for Apple's goals for darwin... they're simple. We want it to be fast. :-)

-pmb

--
"Every time you provide an option, you're asking the user to make a decision.
That means they will have to think about something and decide about it.
It's not necessarily a bad thing, but, in general, you should always try to
minimize the number of decisions that people have to make."
http://joel.editthispage.com/stories/storyReader$51



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.