search for: checksum_

Hello guys, For single scalar pointer parameter, we have 'byval' to specify the pointee is not changed. But for base+range parameters like: declare void @_gfortran_transfer_integer_write(%struct.__st_parameter_dt*, i8*, i32) (This is the fortran runtime api to 'printf' one integer) The 2nd & 3rd args are used to specify the memory of that integer. I didn't find a

Ian, Jeremy, knowing pretty little about networking, it nevertheless seems to me that the different placement of skb_checksum_setup() (in the receive paths of pv-ops vs in various transmit paths in legacy) poses a compatibility problem (nothing done on either side if sending from pv-ops to legacy, and done on both ends when sending from legacy to pv-ops). Am I overlooking something here? Thanks, Jan ____________________...