experience...]
- M_WAIT or M_NOWAIT in memory allocation of mballoc kproc
- Strategy for high watermark wash out
Thanks.
--
Kyunghwan Kim
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
e the conflict.
As you said, it was not difficult and a good chance to practice
programming in kernel. In fact, I'm almost a newbie who just wants
all network device drivers in -current to be mp-safe.
Anyway, it'll be better to wait for your code and learn from you.
Thank you.
--
Kyun
ice private data protection,
and ifnet lock for each ifnet struct protection (such as ifnet.if_mtx).
Maybe these locks should be adaptive or spin
And IFNET_*LOCK() should remain for adding/removing ifnet struct to
the global ifnet whose type is ifnethead.
In case of ifqueue, it should not need to acquire
Is it okay to add INTR_MPSAFE for all INTR_TYPE_NET drivers?
mbuf and bpf routines are all mp-safe, so it seems that
it is safe to make network device drivers out of Giant lock.
Or is there any unresolved related issues?
--
Kyunghwan Kim
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL
version of mb_pop_cont()
that accepts occasionally acquiring Giant?
--
Kyunghwan Kim
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Wed, Dec 18, 2002 at 04:53:00AM +0900, Kyunghwan Kim wrote:
> On Tue, Dec 17, 2002 at 02:31:31PM -0500, Andrew Gallatin wrote:
> > > mbuf and bpf routines are all mp-safe, so it seems that
> > > it is safe to make network device drivers out of Giant lock.
> > &
