From: Minwoo Im <minwoo.im.dev@gmail.com>
To: hch@lst.de, keith.busch@intel.com, sagi@grimberg.me
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 5/5] nvme: add support weighted round robin queue
Date: Thu, 27 Jun 2019 19:37:19 +0900 [thread overview]
Message-ID: <20190627103719.GC4421@minwooim-desktop> (raw)
In-Reply-To: <6e3b0f511a291dd0ce570a6cc5393e10d4509d0e.1561385989.git.zhangweiping@didiglobal.com>
Hi, Maintainers
Would you guys please give some thoughts about this patch? I like this
feature WRR addition to the driver so I really want to hear something
from you guys.
Thanks,
WARNING: multiple messages have this Message-ID (diff)
From: minwoo.im.dev@gmail.com (Minwoo Im)
Subject: [PATCH v3 5/5] nvme: add support weighted round robin queue
Date: Thu, 27 Jun 2019 19:37:19 +0900 [thread overview]
Message-ID: <20190627103719.GC4421@minwooim-desktop> (raw)
In-Reply-To: <6e3b0f511a291dd0ce570a6cc5393e10d4509d0e.1561385989.git.zhangweiping@didiglobal.com>
Hi, Maintainers
Would you guys please give some thoughts about this patch? I like this
feature WRR addition to the driver so I really want to hear something
from you guys.
Thanks,
next prev parent reply other threads:[~2019-06-27 10:37 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1561385989.git.zhangweiping@didiglobal.com>
2019-06-24 14:28 ` [PATCH v3 1/5] block: add weighted round robin for blkcgroup Weiping Zhang
2019-06-24 14:28 ` Weiping Zhang
2019-07-18 13:59 ` Tejun Heo
2019-07-18 13:59 ` Tejun Heo
2019-07-23 14:29 ` Weiping Zhang
2019-07-23 14:29 ` Weiping Zhang
2019-06-24 14:29 ` [PATCH v3 2/5] nvme: add get_ams for nvme_ctrl_ops Weiping Zhang
2019-06-24 14:29 ` Weiping Zhang
2019-06-24 20:12 ` Minwoo Im
2019-06-24 20:12 ` Minwoo Im
2019-06-25 14:46 ` Weiping Zhang
2019-06-25 14:46 ` Weiping Zhang
2019-06-24 14:29 ` [PATCH v3 3/5] nvme-pci: rename module parameter write_queues to read_queues Weiping Zhang
2019-06-24 14:29 ` Weiping Zhang
2019-06-24 20:04 ` Minwoo Im
2019-06-24 20:04 ` Minwoo Im
2019-06-25 14:48 ` Weiping Zhang
2019-06-25 14:48 ` Weiping Zhang
2019-06-26 20:27 ` Minwoo Im
2019-06-26 20:27 ` Minwoo Im
2019-07-14 11:36 ` Minwoo Im
2019-06-24 14:29 ` [PATCH v3 4/5] genirq/affinity: allow driver's discontigous affinity set Weiping Zhang
2019-06-24 14:29 ` Weiping Zhang
2019-06-24 14:29 ` Weiping Zhang
2019-06-24 15:42 ` Thomas Gleixner
2019-06-24 15:42 ` Thomas Gleixner
2019-06-25 2:14 ` Ming Lei
2019-06-25 2:14 ` Ming Lei
2019-06-25 6:13 ` Thomas Gleixner
2019-06-25 6:13 ` Thomas Gleixner
2019-06-25 14:55 ` Weiping Zhang
2019-06-25 14:55 ` Weiping Zhang
2019-06-24 14:29 ` [PATCH v3 5/5] nvme: add support weighted round robin queue Weiping Zhang
2019-06-24 14:29 ` Weiping Zhang
2019-06-24 20:21 ` Minwoo Im
2019-06-24 20:21 ` Minwoo Im
2019-06-25 15:06 ` Weiping Zhang
2019-06-25 15:06 ` Weiping Zhang
2019-06-27 10:37 ` Minwoo Im [this message]
2019-06-27 10:37 ` Minwoo Im
2019-06-27 11:03 ` Christoph Hellwig
2019-06-27 11:03 ` Christoph Hellwig
2019-06-28 15:57 ` Weiping Zhang
2019-06-28 15:57 ` Weiping Zhang
2019-07-10 14:20 ` Weiping Zhang
2019-07-10 14:20 ` Weiping Zhang
2019-07-29 10:22 ` Weiping Zhang
2019-07-29 10:22 ` Weiping Zhang
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=20190627103719.GC4421@minwooim-desktop \
--to=minwoo.im.dev@gmail.com \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.