From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: sebastien dugue <sebastien.dugue-6ktuUTfB/bM@public.gmane.org>
Cc: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Roland Dreier <rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH 1/3] rdma_cm: Add support for a new RDMA_PS_LUSTRE Lustre port space
Date: Thu, 14 Jan 2010 09:25:31 -0800 [thread overview]
Message-ID: <ada3a28mwdw.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <20100114135815.69d5a9a5@frecb007965> (sebastien dugue's message of "Thu, 14 Jan 2010 13:58:15 +0100")
> > I agree. If setting QoS requires a kernel patch for each application, I
> > think we've messed up QoS somehow. There needs to be a way to control
> > QoS via configuration, rather than rebuilding.
>
> Right, it's possible via configuration only, but you then cannot separate
> the different Lustre traffics (MDS and OSS for example).
I guess I don't know enough about Lustre to know why this would be so.
How does creating a new port space for Lustre help with this? Why can't
one do the same thing in one of the existing port spaces?
- R.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-01-14 17:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 14:49 [PATCH 0/3] Add support for specific Lustre Qos sebastien dugue
2010-01-13 14:51 ` [PATCH 1/3] rdma_cm: Add support for a new RDMA_PS_LUSTRE Lustre port space sebastien dugue
2010-01-13 16:56 ` Sean Hefty
[not found] ` <7ED07283D76C422C9210FBE7C832731B-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-01-13 17:04 ` Roland Dreier
[not found] ` <ada6376ndgs.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-01-14 12:58 ` sebastien dugue
2010-01-14 17:25 ` Roland Dreier [this message]
[not found] ` <ada3a28mwdw.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-01-15 7:41 ` sebastien dugue
2010-01-20 1:12 ` Roland Dreier
[not found] ` <adaiqax37g4.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-01-20 7:55 ` sebastien dugue
2010-01-20 8:03 ` Or Gerlitz
[not found] ` <4B56B8E3.3010909-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2010-01-20 9:17 ` sebastien dugue
2010-01-20 15:26 ` Or Gerlitz
[not found] ` <4B572099.3030604-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-01-21 8:28 ` sebastien dugue
2010-01-21 9:12 ` Or Gerlitz
[not found] ` <4B581A68.500-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-01-21 9:26 ` sebastien dugue
2010-01-14 12:47 ` sebastien dugue
2010-01-14 14:09 ` Or Gerlitz
[not found] ` <4B4F25A7.6000900-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-01-14 14:37 ` sebastien dugue
2010-01-13 14:54 ` [PATCH 2/3] opensm/qos_policy: Add a new service ID and keyword for Lustre QoS sebastien dugue
2010-01-13 14:56 ` [PATCH 3/3] Add new port_space parameter to ko2iblnd module sebastien dugue
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=ada3a28mwdw.fsf@roland-alpha.cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rolandd-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=sebastien.dugue-6ktuUTfB/bM@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox