I'm happy to take advice -- I'm really rather new to the patch process, and also this flow separation code. As for the work from the google folks ... is there a good search term or two I can use for this? I've looked for "rxflow separation" and mostly find your own patches.... Chris On Thu, Feb 4, 2010 at 10:28 AM, David Miller <davem@xxxxxxxxxxxxx> wrote: > > Please these patches CC:'d to netdev@xxxxxxxxxxxxxxx > > There is nothing Sparc specific about the NIU driver and > even if it were netdev@xxxxxxxxxxxxxxx is where even platform > specific network device patches are posted. > > Also, your patches which use module parameters to set > things in the NIU chip will need to be deleted. Instead > you should create run-time configuration methods, such > as new ethtool commands and/or flag bits, to modify these > settings. > > Next, it's even more incredulious that you posted this only > to the sparc list given that you make changes to the generic > networking code. > > Finally, there are lots of other work, particularly from the google > folks, to do software flow seperation, which frankly I see no need for > on a chip like NIU which %100 already does this for you in hardware. > > This is a really bad patch submission, sorry. > > Thanks. > -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
