Searched hist:f2a20b166a1efde194b39d8fae5841b843819f4d (Results 1 – 3 of 3) sorted by relevance
| /freebsd/sys/cam/ctl/ |
| H A D | ctl_ser_table.c | diff f2a20b166a1efde194b39d8fae5841b843819f4d Wed Aug 05 23:58:32 CEST 2015 Alexander Motin <mav@FreeBSD.org> Relax serialization of SYNCHRONIZE CACHE commands.
Before this change SYNCHRONIZE CACHE commands were executed exclusively,
as if they had ORDERED tag. But looking through SCSI specs I've found
no any reason to be so strict. For reads this ordering seems pointless.
For writes it looks less obvious, so I left ordering against preceeding
write commands, while following ones are no longer required to wait.
MFC after: 2 weeks
Sponsored by: iXsystems, Inc.
|
| H A D | ctl_cmd_table.c | diff f2a20b166a1efde194b39d8fae5841b843819f4d Wed Aug 05 23:58:32 CEST 2015 Alexander Motin <mav@FreeBSD.org> Relax serialization of SYNCHRONIZE CACHE commands.
Before this change SYNCHRONIZE CACHE commands were executed exclusively,
as if they had ORDERED tag. But looking through SCSI specs I've found
no any reason to be so strict. For reads this ordering seems pointless.
For writes it looks less obvious, so I left ordering against preceeding
write commands, while following ones are no longer required to wait.
MFC after: 2 weeks
Sponsored by: iXsystems, Inc.
|
| H A D | ctl_private.h | diff f2a20b166a1efde194b39d8fae5841b843819f4d Wed Aug 05 23:58:32 CEST 2015 Alexander Motin <mav@FreeBSD.org> Relax serialization of SYNCHRONIZE CACHE commands.
Before this change SYNCHRONIZE CACHE commands were executed exclusively,
as if they had ORDERED tag. But looking through SCSI specs I've found
no any reason to be so strict. For reads this ordering seems pointless.
For writes it looks less obvious, so I left ordering against preceeding
write commands, while following ones are no longer required to wait.
MFC after: 2 weeks
Sponsored by: iXsystems, Inc.
|