linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shirley Ma <xma@us.ibm.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: general@lists.openfabrics.org,
	general-bounces@lists.openfabrics.org,
	linux-kernel@vger.kernel.org
Subject: Re: [ofa-general] Further 2.6.23 merge plans...
Date: Fri, 13 Jul 2007 11:56:57 -0700	[thread overview]
Message-ID: <OF419657E7.3098466C-ON87257317.0067BBE6-88257317.0067EA65@us.ibm.com> (raw)
In-Reply-To: <adahco943ip.fsf@cisco.com>

Hello Roland,

        FYI, we are working on several IPoIB performance improvement 
patches which are not on the list. Some of the patches are under test, 
some of the patches are going to be submitted soon. They are:

1.  skb aggregations for both dev xmit(networking layer) and IPoIB send 
(it will be submitted soon, for both UD and RC mode)
2.  multiple interrupt vectors in IPoIB for multiple links scalability 
(working on patch for both UD and RC mode)
3.  split CQ and send completion aggregation (for both UD and RC mode)
4.  LRO for IPoIB when generic LRO is available in networking layer. (UD 
mode only)

        Some of them might be made in 2.6.23 timeline, some of them might 
not, it depends on our test progress and community review feedback.

Thanks
Shirley

  parent reply	other threads:[~2007-07-13 18:57 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
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   ` Shirley Ma [this message]
2007-07-16 16:47     ` [ofa-general] " 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=OF419657E7.3098466C-ON87257317.0067BBE6-88257317.0067EA65@us.ibm.com \
    --to=xma@us.ibm.com \
    --cc=general-bounces@lists.openfabrics.org \
    --cc=general@lists.openfabrics.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdreier@cisco.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).