On Fri, Aug 05, 2005 at 01:01:57PM -0700, Matt Mackall wrote: > The netpoll philosophy is to assume that its traffic is an absolute > priority - it is better to potentially hang trying to deliver a panic > message than to give up and crash silently.
That would be ok if netpoll was only used to deliver panics. But it is not. It delivers all messages, and you cannot hang the kernel during that. Actually even for panics it is wrong, because often it is more important to reboot in a panic than (with a panic timeout) to actually deliver the panic. That's needed e.g. in a failover cluster. If that was the policy it would be a quite dumb one and make netpoll totally unsuitable for production use. I hope it is not. > > > Also, as Andi told me, the printk here would probably not show up > > anyway if this happens with netconsole. > > That's fine. But in fact, it does show up occassionally - I've seen > it. > > NAK'ed. Too bad. This would mean that all serious non toy users of netpoll would have to carry this patch on their own. But that wouldn't be good. Dave, can you please apply the timeout patch anyways? I suspect Steven's patch for the e1000 is needed in addition to handle different cases too. -Andi - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
