| /freebsd/sys/cam/ctl/ |
| H A D | ctl_frontend_ioctl.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| H A D | ctl_error.h | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| H A D | ctl_tpc_local.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| H A D | ctl_error.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| H A D | ctl_tpc.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| H A D | ctl_frontend_cam_sim.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| H A D | ctl_backend_ramdisk.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| H A D | scsi_ctl.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| H A D | ctl_backend_block.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| H A D | ctl_frontend_iscsi.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| H A D | ctl.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|
| /freebsd/sys/cam/scsi/ |
| H A D | scsi_all.c | diff eb6ac6f9db762bf753e5b6837279f992eb8a5800 Mon Jan 16 17:19:55 CET 2017 Alexander Motin <mav@FreeBSD.org> Make CTL frontends report kern_data_resid for under-/overruns.
It seems like kern_data_resid was never really implemented. This change
finally does it. Now frontends update this field while transferring data,
while CTL/backends getting it can more flexibly handle the result.
At this point behavior should not change significantly, still reporting
errors on write overrun, but that may be changed later, if we decide so.
CAM target frontend still does not properly handle overruns due to CAM API
limitations. We may need to add some fields to struct ccb_accept_tio to
pass information about initiator requested transfer size(s).
MFC after: 2 weeks
|