Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1727319 > unrolled thread

[PATCH] lightnvm: Add error code for bad write pointer

Started by"Javier González" <jg@lightnvm.io>
First post2017-09-06 12:30 +0200
Last post2017-09-06 16:50 +0200
Articles 3 — 3 participants

Back to article view | Back to linux.kernel


Contents

  [PATCH] lightnvm: Add error code for bad write pointer "Javier González" <jg@lightnvm.io> - 2017-09-06 12:30 +0200
    Re: [PATCH] lightnvm: Add error code for bad write pointer Christoph Hellwig <hch@infradead.org> - 2017-09-06 15:50 +0200
      Re: [PATCH] lightnvm: Add error code for bad write pointer Javier González <jg@lightnvm.io> - 2017-09-06 16:50 +0200

#1727319 — [PATCH] lightnvm: Add error code for bad write pointer

From"Javier González" <jg@lightnvm.io>
Date2017-09-06 12:30 +0200
Subject[PATCH] lightnvm: Add error code for bad write pointer
Message-ID<umFKO-lj-19@gated-at.bofh.it>
Add new error code introduced on the OCSSD spec 2.0 for write pointer
mismatch on the device side. This indicates to the host that a write on
a block (chunk) is not respecting the required sequentiality.

Signed-off-by: Javier González <javier@cnexlabs.com>
---
 include/linux/lightnvm.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/include/linux/lightnvm.h b/include/linux/lightnvm.h
index 7dfa56ebbc6d..81b71c6d5873 100644
--- a/include/linux/lightnvm.h
+++ b/include/linux/lightnvm.h
@@ -102,7 +102,8 @@ enum {
 	/* Status codes */
 	NVM_RSP_SUCCESS		= 0x0,
 	NVM_RSP_NOT_CHANGEABLE	= 0x1,
-	NVM_RSP_ERR_FAILWRITE	= 0x40ff,
+	NVM_RSP_ERR_FAILWRITE	= 0x40ff,	/* Generic write failure */
+	NVM_RSP_ERR_FAILWP	= 0x42f0,	/* Write pointer failure */
 	NVM_RSP_ERR_EMPTYPAGE	= 0x42ff,
 	NVM_RSP_ERR_FAILECC	= 0x4281,
 	NVM_RSP_ERR_FAILCRC	= 0x4004,
-- 
2.7.4

[toc] | [next] | [standalone]


#1727491

FromChristoph Hellwig <hch@infradead.org>
Date2017-09-06 15:50 +0200
Message-ID<umISm-2uc-35@gated-at.bofh.it>
In reply to#1727319
On Wed, Sep 06, 2017 at 12:22:38PM +0200, Javier González wrote:
> Add new error code introduced on the OCSSD spec 2.0 for write pointer
> mismatch on the device side. This indicates to the host that a write on
> a block (chunk) is not respecting the required sequentiality.

Do you have a pointer to that spec?

[toc] | [prev] | [next] | [standalone]


#1727558

FromJavier González <jg@lightnvm.io>
Date2017-09-06 16:50 +0200
Message-ID<umJOp-36w-9@gated-at.bofh.it>
In reply to#1727491

[Multipart message — attachments visible in raw view] — view raw

> On 6 Sep 2017, at 15.44, Christoph Hellwig <hch@infradead.org> wrote:
> 
> On Wed, Sep 06, 2017 at 12:22:38PM +0200, Javier González wrote:
>> Add new error code introduced on the OCSSD spec 2.0 for write pointer
>> mismatch on the device side. This indicates to the host that a write on
>> a block (chunk) is not respecting the required sequentiality.
> 
> Do you have a pointer to that spec?

No yet. Still writing it up nicely.

I'll wait to re-post until we have the spec out.

Javier

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web