Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [RFC PATCH 4/4] nvmet: set iopriority for each kiocb for file
Date: Thu, 16 May 2019 09:32:27 +0200	[thread overview]
Message-ID: <20190516073227.GA3922@x250.microfocus.com> (raw)
In-Reply-To: <20190516032109.13048-6-chaitanya.kulkarni@wdc.com>

I'd merge this patch into the previous one.
-- 
Johannes Thumshirn                            SUSE Labs Filesystems
jthumshirn at suse.de                                +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850

  reply	other threads:[~2019-05-16  7:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  3:21 [PATCH RFC 0/4] nvmet: add support for port based io priority Chaitanya Kulkarni
2019-05-16  3:21 ` [RFC PATCH 1/4] nvmet: add iopriority definitions for port Chaitanya Kulkarni
2019-05-16  3:21 ` [PATCH] nvmet: get rid of extra line in the tcp code Chaitanya Kulkarni
2019-05-16  3:22   ` Chaitanya Kulkarni
2019-05-16  3:21 ` [RFC PATCH 2/4] nvmet: allow user to specify ioprioty from cfgfs Chaitanya Kulkarni
2019-05-16  3:21 ` [RFC PATCH 3/4] nvmet: set iopriority for each bio Chaitanya Kulkarni
2019-05-16  3:21 ` [RFC PATCH 4/4] nvmet: set iopriority for each kiocb for file Chaitanya Kulkarni
2019-05-16  7:32   ` Johannes Thumshirn [this message]
2019-05-17  9:45 ` [PATCH RFC 0/4] nvmet: add support for port based io priority Christoph Hellwig
2019-05-17 16:28   ` Chaitanya Kulkarni
2019-05-21  6:56     ` Christoph Hellwig
2019-05-24  8:08   ` Sagi Grimberg

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=20190516073227.GA3922@x250.microfocus.com \
    --to=jthumshirn@suse.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox