Hello,
Mindaugas said:
> Can you explain what the actual problem M_WAIT causes i.e. how would
> it "freeze network stack"?
In M_WAIT case, m_reclaim() will run and run until get mbuf cluster
if mclpool limit reached. If m_reclaim() repeatedly but cannot to
get new mbuf cluster, m_clget() will no
o...@netbsd.org wrote:
> In M_WAIT case, m_reclaim() will run and run until get mbuf cluster
> if mclpool limit reached. If m_reclaim() repeatedly but cannot to
> get new mbuf cluster, m_clget() will not return.
>
> network stacks using mbufs is use with M_DONTWAIT, but it will failed
> to get ne
On Fri, Oct 15, 2010 at 05:30:52PM +0100, Mindaugas Rasiukevicius wrote:
> o...@netbsd.org wrote:
> > In M_WAIT case, m_reclaim() will run and run until get mbuf cluster
> > if mclpool limit reached. If m_reclaim() repeatedly but cannot to
> > get new mbuf cluster, m_clget() will not return.
> >
> In message <20101014004717.7887917...@cvs.netbsd.org>
> on Thu, 14 Oct 2010 00:47:17 +,
> "matthew green" wrote:
> > Module Name:src
> > Committed By: mrg
> > Date: Thu Oct 14 00:47:17 UTC 2010
> >
> > Modified Files:
> > src/sys/kern: subr_disk.
> Modified Files:
> src/sys/arch/bebox/conf: GENERIC majors.bebox
:
> Remove mms and lms from majors.bebox.
Please leave comments that these numbers are reserved like i386
so that we will be able to see if we can (re)use them or not in future.
---
Izumi Tsutsui
