On Thu, May 08, 2008 at 03:13:56PM +0200, Michael Buesch wrote: > > Ok, why is nobody actually answering my _question_? :) > So I'll try to answer it by myself: the hard_start_xmit callback > is actually supposed to return "void", but it returns "int" just > for historical reasons. So there is no way to fail in a TX handler. Pretty much. When lockless drivers were the vogue the return value was useful but as we've since found better ways to scale NICs in an SMP environment (first the tg3 model, and then multi- queue TX) that don't have the problems associated with requeueing the packet, any non-zero return value should only be used by existing code. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
