Hi Jim,
Just started reading this stuff, so it's going to take a while :-)
Meanwhile, first question:
On 20/Nov/09 21:15, Jim Schutt wrote:
Note that the original code assumes that QoS setup is mostly static and
based only on user configuration. As a result, there is no provision for
routing
Hi Sean,
On Wed, 13 Jan 2010 08:56:30 -0800
Sean Hefty sean.he...@intel.com wrote:
This patch adds a new port space for use by Lustre traffic.
This, along with patches to OpenSM and Lustre, allow to define a
specific QoS for lustre.
In general, I don't like the idea of application
Hi Roland.
On Wed, 13 Jan 2010 09:04:19 -0800
Roland Dreier rdre...@cisco.com wrote:
In general, I don't like the idea of application port spaces for QoS
support. Can't this be done using port numbers in the existing port
space?
I agree. If setting QoS requires a kernel patch
sebastien dugue wrote:
That can be done with port numbers, except that we cannot separate
traffic to Lustre MDS and traffic to Lustre OSS
Looking on these patches and going with you for a minute, I don't see how this
patch set serves you to assign a different QoS level (e.g SL) to MDS vs OSS
Signed-off-by: Hal Rosenstock hal.rosenst...@gmail.com
---
diff --git a/infiniband-diags/man/perfquery.8 b/infiniband-diags/man/perfquery.8
index 56615b9..7e9636e 100644
--- a/infiniband-diags/man/perfquery.8
+++ b/infiniband-diags/man/perfquery.8
@@ -6,7 +6,7 @@ perfquery \- query InfiniBand
Hi Eli,
Sorry fot the late response.
If strtol() fails, you may return with an invalid, non zero value for
huge page size. Maybe use some temporary variable to hold the
intermediate result.
If strtol() fails, for any reason, we always return value = 0 for huge page
size.
This indicates that
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
