Hi Dave,
Alan has recommended to get your advise on the possible additional path for
TCP/IP under Linux to support our TCP/IP offload engine iSCSI approach.
Following two questions are something I am looking for and hope you can help
me on the issue.
Basically we have designed TCP/IP offload engine which will by-pass standard
OS TCP/IP layer. The engine suppose to do all task from TCP to NIC,
including copy/checksum/sending/receiving, etc. My questions are specific
related to Linux environment:
1, What could be the point we can plug in a module to let standard TCP/IP
application goes though our special MAC driver
instead of going through OS TCP/IP layer? What should I do to
accomplish the goal?
2, If there is a way to add an additional path to make our offload TCP/IP
engine solution work, please advice what I should do and
what should the packet path flow be (compare with traditional user
application -> socket -> TCP/IP -> MAC driver -> NIC) ?
Following is Alan's suggestion:
> If your engine can do the copy/checksum on receive/send that will be a win
with
> Dave Millers zero copy patches. Best place to ask about this lot is
> <netdev@xxxxxxxxxxx>
Many thanks!
Eddie (Yiding) Wang
SND, Agilent Technologies
3175 Bowers Ave., MS 88C
Santa Clara, Ca 95054
Tel: (408) 970-3059
Fax: (408) 970-3099
E-Mail: yiding_wang@xxxxxxxxxxx
|