Zitat von davidm71 im Beitrag #1844

---

@e.v.o:
Thanks for detailing the proper way to mod efi files into ffs. Was just looking through the EDK2 2015 nvmexpress.c source code and found this:
"Device->Media.WriteCaching = FALSE; ". Wonder if its worth turning that value onto TRUE, recompile and see what happens?

I am tempted to try.

---

@e.v.o

Thanks for offer but I can compile my own no problem. Will test it out later today on a duet bootable USB stick just to be safe. Bet you the write scores go up. Thanks.

@e.v.o

Hi,

Compiled the 2017 EDK2-UDK version of NVMExpress.efi and reran some benchmarks against the older nvme efi driver I use to have and saw like 10-15 percent improvement in scores. Not sure if it was because I disabled that write-cache setting within the nvme driver source code or not. Will have to recompile a fresh copy with it at default settings and get back to you but heres a comparison:


Of course I don't have write cache enabled as I do not own a UPS though have tested with it on within Windows device manager and with it on theres a 3X fold increase in score.

Thanks

EDIT: Added Comparison of Old Driver with Windows Writecaching policy on:



To New EDK2-UDK 2017 NVME driver with Windows Writecaching policy on:


Second edit: Reran 3rd test for accuracy and no seems like theres a statistical tie..

@Fernando, @e.v.o

2017 EDK2 Windows Write Cache ON - Sourcecode WriteCaching:FALSE


2017 EDK2 Windows Write Cache ON - Sourcecode WriteCaching:TRUE


2017 EDK2 Windows Write Cache OFF - Source Code Write Caching TRUE:


2017 EDK2 Windows Write Cache OFF - Source Code Write Caching FALSE:


So it would seem that modifying the source code to turn on the Media.Writecaching Key may not do anything and in fact result in slightly lower scores
for both when write cache is turned on or off in device manager. However the new EDK2017 driver is definitely faster than the old one!

Thanks

Hmm. I'll look again. I"m looking for that 8c8ce line to do my work in..

Updated my benchmarks and corrected any statistical errors and reran tests for accuracy. My results show no real advantage over the old Nvme efi driver and the new 2017 edk driver. At least on my system which is on an X58 EVGA Classified loading the Plextor M8PeY through a Duet bootloader so there could be a bottleneck effect limiting my scores or any advantages fwiw. Anyhow here is a link to the new 2017 edk2 nvme drivers in Efi form if anyone wants to use them. They still need to be converted to ffs for insertion in ones bios.

Thanks @Fernando,

I would suggest the non modded Writecaching Off version because it seemed like the scores were slightly worse with writecaching on though could be statistically the same but my scores showed an advantage to the normal version which would be as the author of the driver intended its use as in that form. I can't say what if turning on writecaching in the efi driver would do or if it would be safe,

Thanks

I have the April Bios and I have a ready to go Samsung 950 pro ready to go. I was going to try and test it later this evening but if you or someone else wants to add the new module to the BiOs I uploaded here feel free and I can test it. Otherwise I will tinker with it later. I'm 99% positive I will have to remove something to keep the size under the limit. I will follow the guide on what possible things I can take out.

Of course I was going to use the module from page one.

@Fernando,

Was just having fun. Thank you for your comments. Got something else in the works. Thanks.

Well here is my attempt. Everything looks right but when I tried to flash it gave me invalid BIOS file. I have tried it both with the extensions of .211 (which is how it is straight from Asus) and as .ROM. Neither works. It looks to be the same size as the original so I didn't get a size error.

I went ahead and added the .ffs file and got no size error so I don't think I need to take anything out.

The actual file name straight from Asus has an extension of .211 which is the bios revision. The previous version was .210 so there is no .ROM or .CAP. I can update from version .210 to .211 and back with no issues so I'm missing something. :(

Suggestions?

EDIT ** Looking at the different ways to 'flash' a bios I see that Asus has instructions for .Rom/.CAP and Gigabyte has instructions for the APTIO MB. I have an Asus Aptio with EZ Flash in the BIOS which has worked and is the preferred method. Is there a BIOS flash right up for Asus APTIO mbs?