From: Yan Li <yanli@ascar.io>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] [PATCH 1/6] Autoconf option for rate-limiting Quality of Service (RLQOS)
Date: Wed, 22 Mar 2017 07:19:51 -0700 [thread overview]
Message-ID: <b2087803-6426-bc07-e349-13a4c7b42d8f@ascar.io> (raw)
In-Reply-To: <D4F6FF83.CB29%jevans@cray.com>
On 03/21/2017 01:09 PM, Ben Evans wrote:
> I would remove the #ifdef ENABLE_RLQOS blocks, especially in lustre_idl.h
> since you're proposing to add new fields and consume some of the padding
> bits. It will cause a lot of headache for the next feature that comes
> along and consumes some of those bits.
Yeah, that's a good point. I'll remove it if all are ok with this.
Yan
next prev parent reply other threads:[~2017-03-22 14:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 19:43 [lustre-devel] [PATCH 0/6] Rate-limiting Quality of Service Yan Li
2017-03-21 19:43 ` [lustre-devel] [PATCH 1/6] Autoconf option for rate-limiting Quality of Service (RLQOS) Yan Li
2017-03-21 20:09 ` Ben Evans
2017-03-22 14:19 ` Yan Li [this message]
2017-03-22 14:27 ` Ben Evans
2017-03-24 22:22 ` Dilger, Andreas
[not found] ` <3BE4A898-D944-41F9-84C8-FE8DA80D0D65@datadirectnet.com>
2017-04-14 2:55 ` Yan Li
2017-04-17 12:32 ` Brinkmann, Prof. Dr. André
2017-04-17 16:46 ` Yan Li
2017-04-21 12:50 ` Brinkmann, Prof. Dr. André
2017-03-21 19:43 ` [lustre-devel] [PATCH 2/6] Added fields to message for RLQOS support Yan Li
2017-03-23 14:54 ` Alexey Lyashkov
2017-03-21 19:43 ` [lustre-devel] [PATCH 3/6] RLQOS main data structure Yan Li
2017-03-21 19:43 ` [lustre-devel] [PATCH 4/6] lprocfs interfaces for showing, parsing, and controlling rules Yan Li
2017-03-21 19:43 ` [lustre-devel] [PATCH 5/6] Throttle the outgoing requests according to tau Yan Li
2017-03-23 14:03 ` Alexey Lyashkov
2017-03-21 19:43 ` [lustre-devel] [PATCH 6/6] Adjust max_rpcs_in_flight according to metrics Yan Li
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=b2087803-6426-bc07-e349-13a4c7b42d8f@ascar.io \
--to=yanli@ascar.io \
--cc=lustre-devel@lists.lustre.org \
/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.