Masa Murayama wrote: > ----- Original Message ----- >> Date: Wed, 12 Mar 2008 14:31:21 +0530 >> From: "Nabil Rahiman" <[EMAIL PROTECTED]> >> To: driver-discuss@opensolaris.org >> Subject: [driver-discuss] EthernetDirver-packet-tcp_mss >> >> >> Hi, >> >> I am writing for device driver for an Ethernet chip. It is required TCP >> MSS value of the packet for sending across the network. >> Is there any routine/macro for accessing the TC MSS field of a >> packet(always stored at end of tcp header.). >> In linux it is available, hope same type routine or macro is available in >> Solaris too. >> > > I guess you are planning to use TCP large send offloading. > If yes, you can get mss by hcksum_retrieve(). > For detail, please refer xge driver, especially uts/common/io/xge/drv/xgell.c
Yes, for LSO packets, mss can be gotten through hcksum_retrieve(). What hareware offload capabilities does your hareware support? What information does your device need to support different level hardware offload? The reason for my questions is that there're internal requirements to enhance the implementation of hcksum_retrieve() and hcksum_assoc(). So I'm soliciting the inputs of guys who work on drivers to make the interfaces as general as possible. I'm quite sure that Paul, Drew, and Tom can contribute to this. Please let me know if I'm not clear here.:-) Thanks, Lucy ' > > If not, I don't know how to get mss from mblk_t, sorry. I think there is > no formal way to refer data structures in tcp from mblk_t. > > -masa > >> ----- inline ----- >> _______________________________________________ >> driver-discuss mailing list >> driver-discuss@opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/driver-discuss > > _______________________________________________ > driver-discuss mailing list > driver-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/driver-discuss > _______________________________________________ driver-discuss mailing list driver-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/driver-discuss
