Bosko Milekic writes: > > back. We'll also need a kproc that can wake up every now and then to > > expand the pool if allocations at interrupt time failed. Or do you > > already have a mechanism for that? > > The intended mechanism is the kproc and when the allocator was first > designed and written, I had taken that into account although I have <...> > (I hope that came out OK). As you can see, the concept is very simple > and with the current infrastructure should be fairly easy to > implement. If you're wondering, I was going to do is as a 5.1 feature > at some point because I've been so swamped with other things right now > and so I do not foresee being able to do this in time for 5.0.
This looks ideal. I'm looking forward to it. > It is not out of date. The code means: > > "If you've given me a counter then I'll use it otherwise I'll try to > allocate one with malloc()." Ah, duh. Thanks. I'd better start providing one in my driver then.. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
