linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean Hefty <mshefty@ichips.intel.com>
To: Sean Hefty <sean.hefty@intel.com>
Cc: "'Roland Dreier'" <rdreier@cisco.com>,
	Or Gerlitz <or.gerlitz@gmail.com>,
	linux-kernel@vger.kernel.org, general@lists.openfabrics.org
Subject: Re: [ofa-general] Further 2.6.23 merge plans...
Date: Wed, 18 Jul 2007 10:05:58 -0700	[thread overview]
Message-ID: <469E4876.7020805@ichips.intel.com> (raw)
In-Reply-To: <000001c7c8fc$360eec90$5dcc180a@amr.corp.intel.com>

> We will have a better idea of the issues and possible solutions once the QoS
> spec is released, and we can hold discussions on it.  I will be working more
> details on QoS enhancements starting in the next couple of weeks. 

Based on discussions so far, maybe the best path forward from here is to
delay until 2.6.24.  This will let us add this version to OFED 1.3 for
more widespread testing, plus give us the time that we need to come up
with a plan to integrate QoS with the local SA.  I don't think we'll
have a final implementation for QoS support by that time, but at least
we'll have a better idea of the problems.

These patches are based on the same design used with OFED 1.2, but a
fair number of lines of code still changed, plus it added InformInfo 
registration.  I don't believe anyone other than me has tested these 
patches with the local SA enabled.  It's typically running on my 
systems, but because it automatically fails over to standard SA queries, 
it would be easy for me to miss problems.

- Sean

  reply	other threads:[~2007-07-18 17:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 23:07 [GIT PULL] please pull infiniband.git Roland Dreier
2007-07-12 23:15 ` Further 2.6.23 merge plans Roland Dreier
2007-07-13  0:17   ` [ofa-general] " Hal Rosenstock
2007-07-13  1:14   ` Sean Hefty
     [not found]     ` <15ddcffd0707172020j5b68fcb2v7d3ca77863998020@mail.gmail.com>
2007-07-18  3:23       ` Roland Dreier
2007-07-18  5:26         ` Sean Hefty
2007-07-18 17:05           ` Sean Hefty [this message]
2007-07-18 20:54             ` Sean Hefty
2007-07-13  5:47   ` Michael S. Tsirkin
2007-07-13 18:14     ` Roland Dreier
2007-07-13 18:50       ` [ofa-general] " Shirley Ma
2007-07-17 18:06         ` Roland Dreier
2007-07-14 17:54       ` Michael S. Tsirkin
     [not found]         ` <OF72F6B9D1.F60C4EEF-ON8725731A.00506757-8825731A.0024BD1C@us.ibm.com>
2007-07-16 14:55           ` [ofa-general] " Michael S. Tsirkin
2007-07-16 16:42         ` Roland Dreier
2007-07-16 20:05           ` Michael S. Tsirkin
2007-07-17 17:53             ` Roland Dreier
2007-07-13 18:56   ` [ofa-general] " Shirley Ma
2007-07-16 16:47     ` Roland Dreier
2007-07-15 12:26   ` Tziporet Koren
2007-07-16 16:42     ` Roland Dreier
2007-07-17 18:07   ` Roland Dreier
2007-07-17 20:43     ` Matt Leininger
2007-07-17 20:45       ` Roland Dreier
2007-07-18  6:36         ` Or Gerlitz
2007-07-17 21:44     ` Michael S. Tsirkin
2007-07-18  7:34       ` [ofa-general] " Tziporet Koren
2007-07-18  7:38         ` Michael S. Tsirkin
2007-07-18  8:48           ` Tziporet Koren
2007-07-18 16:16             ` Sean Hefty
2007-07-18 16:20               ` Roland Dreier

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=469E4876.7020805@ichips.intel.com \
    --to=mshefty@ichips.intel.com \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=or.gerlitz@gmail.com \
    --cc=rdreier@cisco.com \
    --cc=sean.hefty@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).