Re: [U-Boot] [PATCH] nvme: Fix PRP Offset Invalid

2019-08-22 Thread Bin Meng
HI Aaron, On Thu, Aug 22, 2019 at 5:12 PM Aaron Williams wrote: > > When large writes take place I saw a Samsung EVO 970+ return a status > value of 0x13, PRP Offset Invalid. I tracked this down to the > improper handling of PRP entries. The blocks the PRP entries are > placed in cannot cross

Re: [U-Boot] [PATCH] nvme: Fix PRP Offset Invalid

2019-08-22 Thread Aaron Williams
I'm sorry about the messed up subject saying [PATCH]. For some reason git send-email is mangling the subject line. I'm new to trying to use this method to send out patches. This is version 2 of my patch. -Aaron On Thursday, August 22, 2019 2:12:32 AM PDT Aaron Williams wrote: > When large

[U-Boot] [PATCH] nvme: Fix PRP Offset Invalid

2019-08-22 Thread Aaron Williams
When large writes take place I saw a Samsung EVO 970+ return a status value of 0x13, PRP Offset Invalid. I tracked this down to the improper handling of PRP entries. The blocks the PRP entries are placed in cannot cross a page boundary and thus should be allocated on page boundaries. This is

[U-Boot] [PATCH] nvme: Fix PRP Offset Invalid

2019-08-21 Thread Aaron Williams
From: Aaron Williams When large writes take place I saw a Samsung EVO 970+ return a status value of 0x13, PRP Offset Invalid. I tracked this down to the improper handling of PRP entries. The blocks the PRP entries are placed in cannot cross a page boundary and thus should be allocated on page

Re: [U-Boot] [PATCH] nvme: Fix PRP Offset Invalid

2019-08-21 Thread Bin Meng
Hi Aaron, On Wed, Aug 21, 2019 at 10:09 PM Aaron Williams wrote: > > From: Aaron Williams > > When large writes take place I saw a Samsung EVO 970+ return a status > value of 0x13, PRP Offset Invalid. I tracked this down to the > improper handling of PRP entries. The blocks the PRP entries

[U-Boot] [PATCH] nvme: Fix PRP Offset Invalid

2019-08-21 Thread Aaron Williams
From: Aaron Williams When large writes take place I saw a Samsung EVO 970+ return a status value of 0x13, PRP Offset Invalid. I tracked this down to the improper handling of PRP entries. The blocks the PRP entries are placed in cannot cross a page boundary and thus should be allocated on page

[U-Boot] [PATCH] nvme: Fix PRP Offset Invalid

2019-08-21 Thread Aaron Williams
From: Aaron Williams When large writes take place I saw a Samsung EVO 970+ return a status value of 0x13, PRP Offset Invalid. I tracked this down to the improper handling of PRP entries. The blocks the PRP entries are placed in cannot cross a page boundary and thus should be allocated on page

[U-Boot] [PATCH] nvme: Fix PRP Offset Invalid

2019-08-21 Thread Aaron Williams
From: Aaron Williams When large writes take place I saw a Samsung EVO 970+ return a status value of 0x13, PRP Offset Invalid. I tracked this down to the improper handling of PRP entries. The blocks the PRP entries are placed in cannot cross a page boundary and thus should be allocated on page

[U-Boot] [PATCH] nvme: Fix PRP Offset Invalid

2019-08-20 Thread Aaron Williams
When large writes take place I saw a Samsung EVO 970+ return a status value of 0x13, PRP Offset Invalid. I tracked this down to the improper handling of PRP entries. The blocks the PRP entries are placed in cannot cross a page boundary and thus should be allocated on page boundaries. This is