{"push_id":1345858290,"size":1,"distinct_size":1,"ref":"refs/heads/leaf-1","head":"fbc7e056ed22ce3eb3924293733571a12eee7363","before":"d961f6f64d965d51a970b4354ab8ca458a03a36b","commits":[{"sha":"fbc7e056ed22ce3eb3924293733571a12eee7363","author":{"name":"Subash Abhinov Kasiviswanathan","email":"cb27acb5bfbe78054ecbc5d329a00e60c1019de9@codeaurora.org"},"message":"clatd: Add support for handling GRO coalesced packets\n\nWith this change, we can notify network stack to disable checksum\nvalidation for GRO packets as well as other packets which have\nchecksum validation completed earlier in a driver.\n\nGRO packets have the ip_summed field set to CHECKSUM_PARTIAL while\nchecksum offloaded packets have the ip_summed field as\nCHECKSUM_UNNECESSARY. Kernel copies this ip_summed field to the\nstatus field in the tpacket filter. The information from the status\nfield is then passed as part of the TUN header to the TUN interface.\n\nAny other packet will have the complete checksum validation done\nin the network stack. Note that this only applies to packets which\nare captured in packet sockets and passed onto the TUN interface.\n\nMTU serves a dual purpose for CLAT. The segment size of the packet\nring is based on the MAXMTU apart from the interface MTU itself.\n\nGRO coalesce happens on the receive path which is not affected by\nthe MTU (transmit). In other words, increasing the MAXMTU does not\naffect if a GRO coalesced packet is delivered to CLAT.\nIt only affects the amount of data being read from the TPacket ring.\n\nIntroduce a new parameter MAXMRU which handles the increased MRU\nto account for GRO packets. Increase the ring size to compensate\nfor the larger segments to maintain the same throughput as earlier\n\nCRs-Fixed: 1023199\nChange-Id: I5f5ff05918f3d3e03bb18fe799ccb5770a85038a","distinct":true,"url":"https://api.github.com/repos/TeamLeaf/android_external_android-clat/commits/fbc7e056ed22ce3eb3924293733571a12eee7363"}]}
{"actor":{"display_login":"CNBLACK"}}