On Thu, May 15, 2008 at 11:00:46PM +0530, subbu wrote:We do not recommend it, but recommend to write Linux specific drivers. Operating systems are quite different and you get far better drivers if you really optimize them for specific OS. That's especially important for performance critical drivers like yours for high speed networking. Also splitting drivers into generic and OS specific parts typically leads to poor and overcomplicated design. Anyways if you really want abstraction elsewhere then use the Linux names for it. But it's really not recommended. -Andi -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Linus Torvalds | Linux 2.6.27-rc8 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Linux 2.6.20-rc6 |
| Mike Snitzer | Re: Distributed storage. |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Herbert Xu | Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state ch... |
