I read the latter half of your reply now. Yes, we have iscsi_sw_data_recv as the recv_actor function. Thanks for the reply.
On Fri, Jun 22, 2012 at 11:03 AM, narender <narender.mehr...@gmail.com>wrote: > Thanks for the prompt reply. > > The kernel we are using is Suse 11 SP 2 . This problem is seen > intermittently after a few read have completed. > The callback never gets called resulting in a SCSI timeout. > > Is there a pointer to the patch that I can get. That would be highly > appreciated.Thanks again. > > > > On Thursday, June 21, 2012 7:52:14 PM UTC+5:30, Mike Christie wrote: >> >> On 06/21/2012 07:39 AM, narender wrote: >> > Am using open-iscsi on Suse 10.2, while doing IO, in receive path, the >> > function iscsi_sw_tcp_recv is not getting called by the tcp_read_sock >> > function. It manifests in the receive path (Data-in PDUs processing) >> but >> > does not always happens at the same moment every time I have put some >> > printks in the kernel for debugging and I can see that data is >> available in >> > the socket to be read and socket state is also normal, but >> tcp_read_sock is >> > not calling the function iscsi_sw_tcp_recv to receive the data. The >> > recv_actor function is not getting invoked after a point in time. >> > Any pointers in this regard will be highly appreciated. >> > >> >> Does it never get called then? So do we end up getting those iscsi >> ping/nop errors or does a scsi command timeout and then we run the eh? >> >> What kernel is this with? A SUSE engineer sent a patch for something >> like this a while back. >> >> Author: Mike Christie <micha...@cs.wisc.edu> >> Date: Tue May 2 19:46:49 2006 -0500 >> >> [SCSI] iscsi: dequeue all buffers from queue >> >> >> In this patch we set the sock up, so that it would always call the actor >> function (we used to try to track how many bytes we should be reading). >> If you have iscsi_sw_tcp_recv instead of the older iscsi_tcp_data_recv >> then I think you should have the patch. >> >> If you have that patch then you might have to contact SUSE (I can send >> you some email addresses), because I am not sure what their tcp/ip code >> does. I am not even sure what iscsi code is in there are you can tell >> from my questions :) >> > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To post to this group, send email to email@example.com. To unsubscribe from this group, send email to open-iscsi+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/open-iscsi?hl=en.