All of lore.kernel.org
 help / color / mirror / Atom feed
From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH V2 2/3] lnvm: introduce chunk-log command for chunk info
Date: Sun, 28 Jul 2019 12:18:22 +0900	[thread overview]
Message-ID: <20190728031822.GC24390@minwoo-desktop> (raw)
In-Reply-To: <8276ea2a-990d-3aae-b144-54986153e834@lightnvm.io>

Hi Matias,

> > +static inline const char *print_chunk_type(__u8 ct)
> > +{
> > +	switch (ct) {
> > +	case 1 << 0:	return "SEQWRITE_REQ";
> > +	case 1 << 1:	return "RANDWRITE_ALLOWED";
> > +	case 1 << 4:	return "DEVIATED";
> > +	default:	return "UNKNOWN";
> > +	}
> > +}
> 
> The Chunk Type is divided into two value ranges - one for the chunk type
> (seq, req) and one that describes the properties of the zone. I would move
> the "Deviated" into being expressed as an attribute (or similar). Then they
> are clearly separated. An OCSSD implementation can both have the SEQ write
> bit set, together with bit 4 for dynamic chunk capacity. The above doesn't
> communicate that in the right way.

Ah sorry, I think my brain was not working well in the dawn ;).  I'll
provide "Deviated" things as an attribute first regardless the chunk
types.

Thanks for the review.  Will prepare the next version.

  reply	other threads:[~2019-07-28  3:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 19:32 [PATCH V2 0/3] nvme-cli: lnvm: introduce chunk-log command Minwoo Im
2019-07-27 19:32 ` [PATCH V2 1/3] lnvm: make data_len to sizeof() instead of magic number Minwoo Im
2019-07-27 19:32 ` [PATCH V2 2/3] lnvm: introduce chunk-log command for chunk info Minwoo Im
2019-07-27 19:52   ` Matias Bjørling
2019-07-28  3:18     ` Minwoo Im [this message]
2019-07-27 19:32 ` [PATCH V2 3/3] lnvm: introduce alias geometry for id-ns for lnvm Minwoo Im
2019-07-27 19:53   ` Matias Bjørling

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190728031822.GC24390@minwoo-desktop \
    --to=minwoo.im.dev@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.