Re: mbufs eaten up - when pinging

1999-08-24 Thread Luigi Rizzo
> > 'no buffer space' often comes when the output IFQ is full, which is > > between 20 and 50 buffers. Are you sure you are seeing more than those > > mbufs in use ? > > It occurs when about 105/128 mbufs (94%) are used. ok, that's reasonable, with 50 bufs in the output queue and perhaps a matchi

Re: mbufs eaten up - when pinging

1999-08-24 Thread Luigi Rizzo
> > 'no buffer space' often comes when the output IFQ is full, which is > > between 20 and 50 buffers. Are you sure you are seeing more than those > > mbufs in use ? > > It occurs when about 105/128 mbufs (94%) are used. ok, that's reasonable, with 50 bufs in the output queue and perhaps a match

Re: mbufs eaten up - when pinging

1999-08-24 Thread Christoph Kukulies
On Tue, Aug 24, 1999 at 04:47:03PM +0200, Luigi Rizzo wrote: > > With a non-functioning route over isdn (i4b) I'm observing > > that mbufs allocated soon reach the limit and then I'm getting > > 'no buffer space' available. I'm not sure whether > > 'no buffer space' often comes when the output IFQ

Re: mbufs eaten up - when pinging

1999-08-24 Thread Christoph Kukulies
On Tue, Aug 24, 1999 at 04:47:03PM +0200, Luigi Rizzo wrote: > > With a non-functioning route over isdn (i4b) I'm observing > > that mbufs allocated soon reach the limit and then I'm getting > > 'no buffer space' available. I'm not sure whether > > 'no buffer space' often comes when the output IF

Re: mbufs eaten up - when pinging

1999-08-24 Thread Gary Jennejohn
Christoph Kukulies writes: > >With a non-functioning route over isdn (i4b) I'm observing >that mbufs allocated soon reach the limit and then I'm getting >'no buffer space' available. I'm not sure whether >the networking stack is still usable for other purposes >but I prefer to reboot. > >I just wan

Re: mbufs eaten up - when pinging

1999-08-24 Thread Gary Jennejohn
Christoph Kukulies writes: > >With a non-functioning route over isdn (i4b) I'm observing >that mbufs allocated soon reach the limit and then I'm getting >'no buffer space' available. I'm not sure whether >the networking stack is still usable for other purposes >but I prefer to reboot. > >I just wa

Re: mbufs eaten up - when pinging

1999-08-24 Thread Luigi Rizzo
> With a non-functioning route over isdn (i4b) I'm observing > that mbufs allocated soon reach the limit and then I'm getting > 'no buffer space' available. I'm not sure whether 'no buffer space' often comes when the output IFQ is full, which is between 20 and 50 buffers. Are you sure you are seei

Re: mbufs eaten up - when pinging

1999-08-24 Thread Luigi Rizzo
> With a non-functioning route over isdn (i4b) I'm observing > that mbufs allocated soon reach the limit and then I'm getting > 'no buffer space' available. I'm not sure whether 'no buffer space' often comes when the output IFQ is full, which is between 20 and 50 buffers. Are you sure you are see

mbufs eaten up - when pinging

1999-08-24 Thread Christoph Kukulies
With a non-functioning route over isdn (i4b) I'm observing that mbufs allocated soon reach the limit and then I'm getting 'no buffer space' available. I'm not sure whether the networking stack is still usable for other purposes but I prefer to reboot. I just want to bring up this issue because it

mbufs eaten up - when pinging

1999-08-24 Thread Christoph Kukulies
With a non-functioning route over isdn (i4b) I'm observing that mbufs allocated soon reach the limit and then I'm getting 'no buffer space' available. I'm not sure whether the networking stack is still usable for other purposes but I prefer to reboot. I just want to bring up this issue because i