Andi Kleen writes: > Or did I misunderstand you? What is wrong with making methods, keyed off of the ethernet protocol ID, that can do the "I know where/how-long headers are" stuff for that protocol? Only cards with the problem call into this function vector or however we arrange it, and then for those that don't have these problems at all we can make NULL a special value for this "post-header" pointer. You can pick some arbitrary number, sure, that is another way to do it. Such a size would need to be chosen very carefully though. Later, David S. Miller [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Re: LILO error with 2.4.3-pre... Mircea Damian
- Re: LILO error with 2.4.3-pre... Guest section DW
- RE: LILO error with 2.4.3-pre1... Andre Tomt
- Re: LILO error with 2.4.3-pre... Steven J. Hill
- Re: LILO error with 2.4.3-pre1... Alan Cox
- Re: New net features for added performance Jeff Garzik
- Re: New net features for added performance Andi Kleen
- Re: New net features for added performance Rusty Russell
- Re: New net features for added performance David S. Miller
- Re: New net features for added performance Andi Kleen
- Re: New net features for added performance David S. Miller
- Re: New net features for added perform... Jeremy Jackson
- Re: New net features for added performance kuznet
- Re: New net features for added performance Michael Richardson
- Re: New net features for added performance Jeremy Jackson
- Re: New net features for added performance Werner Almesberger
- Re: New net features for added performance Jonathan Morton
- Re: New net features for added performance Noah Romer
- Re: New net features for added performance Jes Sorensen
- Re: New net features for added performance Andrew Morton
- Re: New net features for added performance Jeremy Jackson