Hello Laszlo,
Thanks for the quick response. I have some doubts regarding
"TransactionStatus" that should be signaled by the driver when an IO
operation is completed. If my understanding is not correct please educate.
1. As per UEFI spec, the error codes EFI_DEVICE_ERROR, EFI_NO_MEDIA,
EFI_MEDIA_CHANGED or EFI_WRITE_PROTECTED should not be signaled when non
Blocking IO is being used. so if an IO fails, the driver should not signal
the event as per the spec. if this is the case,
the event should be signaled only when IO is completed successfully ?
2. If the driver does not have enough resources to complete an IO request,
the driver should signal the event with same status (EFI_OUT_OF_RESOURCES)
so that caller will retry the IO ? In such cases, what should be the status
of ReadEx/WriteEx callbacks itself that should returned to the caller ?
In short, i am bit confused what should be the "Transaction Status" that
should be signaled by the driver. Please comment.
Thanks,
Sajeesh.
On Mon, Jan 28, 2019 at 2:17 PM Laszlo Ersek <ler...@redhat.com> wrote:
> Hi,
>
> On 01/26/19 17:57, Sajeesh Kk wrote:
> > Hello Rafeal,
> >
> > I believe The UEFI Sct test suite cannot be used for performance testing.
> > Are there any tools which can be used from UEFI shell to measure disk IO
> > perfomance using BlockIO2 Protocol ?
> > Please let me know.
>
> from a cursory look, FatPkg/EnhancedFatDxe appears to implement the the
> ReadEx/WriteEx methods of EFI_FILE_PROTOCOL
> (EFI_FILE_PROTOCOL_REVISION2). I think the implementation uses the
> DiskIo2 protocol.
>
> And "MdeModulePkg/Universal/Disk/DiskIoDxe" should automatically install
> DiskIo2 on top of your BlockIo2.
>
> So, if you can write a simple UEFI application that uses the *Ex()
> methods of EFI_FILE_PROTOCOL, that could be a start. (Nothing in edk2
> seems to use ReadEx / WriteEx currently.)
>
> Thanks,
> Laszlo
>
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
