No DHCPOFFERS received.

2006-07-31 Thread Alexandre Martins Garcia
Hello everybody, I have a modem connected to my freebsd machine in ethernet, so to have a configuration from my ISP I did: hydrus[/home/amg]# dhclient fxp0 DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 11 DHCPDISCOVER on fxp0

Re: Changes in the network interface queueing handoff model

2006-07-31 Thread John-Mark Gurney
Robert Watson wrote this message on Mon, Jul 31, 2006 at 18:08 +0100: > >I question whether you need a fallback software if_snd queue at all for > >modern devices such as the Intel and Broadcom gigabit chips. The hardware > >transmit descriptor rings typically have sizes of the order of 256 > >

Re: Changes in the network interface queueing handoff model

2006-07-31 Thread John Polstra
On 31-Jul-2006 Petri Helenius wrote: > Robert Watson wrote: >> >> I tend to agree, but implemented full queueing support for if_em to >> make sure I understood to complexity implications of completely >> removing queueing from the ifnet side dispatch. I guess an >> interesting question for us i

Re: Changes in the network interface queueing handoff model

2006-07-31 Thread Petri Helenius
Robert Watson wrote: I tend to agree, but implemented full queueing support for if_em to make sure I understood to complexity implications of completely removing queueing from the ifnet side dispatch. I guess an interesting question for us is how we decide what the right threshold is to imp

RE: Changes in the network interface queueing handoff model

2006-07-31 Thread Robert Watson
On Mon, 31 Jul 2006, John Polstra wrote: Attached is a patch that maintains the current if_start, but adds if_startmbuf. If a device driver implements if_startmbuf and the global sysctl net.startmbuf_enabled is set to 1, then the if_startmbuf path in the driver will be used. Otherwise, if_st

RE: Changes in the network interface queueing handoff model

2006-07-31 Thread John Polstra
> Attached is a patch that maintains the current if_start, but adds > if_startmbuf. If a device driver implements if_startmbuf and the global > sysctl net.startmbuf_enabled is set to 1, then the if_startmbuf path in the > driver will be used. Otherwise, if_start is used. I have modified the i

Current problem reports assigned to you

2006-07-31 Thread FreeBSD bugmaster
Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description --- o [2006/01/30] kern/92552 net A serious bug in most network drivers fro f [2006/02/12] kern

Re: Changes in the network interface queueing handoff model

2006-07-31 Thread Robert Watson
On Sun, 30 Jul 2006, Sam Leffler wrote: I'm a little uncomfortable with our current m_tag model, as it requires significant numbers of additional allocations and frees for each packet, as well as walking link lists. It's fine for occasional discretionary use (i.e., MAC labels), but I worry a

Re: Changes in the network interface queueing handoff model

2006-07-31 Thread Robert Watson
On Mon, 31 Jul 2006, Hans Petter Selasky wrote: On Sunday 30 July 2006 21:23, Robert Watson wrote: On Sun, 30 Jul 2006, Sam Leffler wrote: Just a comment while the iron is hot: Maybe you can make the network model safe against detach. Currently I see that the processor can be stuck in rout

Re: Changes in the network interface queueing handoff model

2006-07-31 Thread Hans Petter Selasky
On Sunday 30 July 2006 21:23, Robert Watson wrote: > On Sun, 30 Jul 2006, Sam Leffler wrote: Just a comment while the iron is hot: Maybe you can make the network model safe against detach. Currently I see that the processor can be stuck in routines like "if_start" after that "if_free()" has bee