All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Grover <andy.grover-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
	Chris Mason <chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Subject: Re: RDS/IB: add _to_node() macros for numa and use {k,v}malloc_node()
Date: Tue, 14 Sep 2010 16:53:20 -0700	[thread overview]
Message-ID: <4C900AF0.2040908@oracle.com> (raw)
In-Reply-To: <4C8C94B8.9030107-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>

On 09/12/2010 01:52 AM, Or Gerlitz wrote:
> Hi Andy, looking on this net-next-2.6 patch, I wonder if you can
> elaborate on your "significantly helps performance" comment - what
> improvement you see with this patch?

 > What about the QP/CQ memory, are they better be placed in node-local
 > to the HCA manner?

Hi Or, I'm afraid I don't have exact numbers for you.. those changes 
were part of a series of tweaks and fixes for bottlenecks in rds code.

On our numa box, the HCA is attached to a particular package of CPUs & 
memory. Having the in-memory structures that the hca is accessing in 
node-local RAM seemed to measurably help, although reducing contention 
helped even more. Chris Mason says it seemed like init-time allocations 
seemed to benefit while runtime allocations were not helped, or even hurt.

Clearly this is not enough data to go on, beyond the conclusion that yes 
it's something that should be looked at more closely. Big machines are 
still rather scarce, which makes it harder.

Regards -- Andy
--
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

  parent reply	other threads:[~2010-09-14 23:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 18:51 net-next pull request: RDS Andy Grover
     [not found] ` <4C892C9C.4060304-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2010-09-09 21:58   ` David Miller
2010-09-12  8:49   ` Or Gerlitz
2010-09-13 17:14     ` [rds-devel] " Chris Mason
     [not found]     ` <4C8C9422.2070306-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-09-12  8:52       ` RDS/IB: add _to_node() macros for numa and use {k,v}malloc_node() Or Gerlitz
     [not found]         ` <4C8C94B8.9030107-hKgKHo2Ms0FWk0Htik3J/w@public.gmane.org>
2010-09-14 23:53           ` Andy Grover [this message]
2010-09-14 18:35       ` [rds-devel] net-next pull request: RDS Zach Brown
     [not found]         ` <20100914183514.GA3417-Mg0Rv1oTIzK+NQz5YmTpAAHTzkgPINtM@public.gmane.org>
2010-09-14 22:28           ` Andrew Grover
     [not found]             ` <AANLkTin69m0kK6bqUiwYeHRQT0Ehso16xA6RBtBFFgW3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-09-14 23:10               ` Roland Dreier
2010-09-15  9:22               ` Or Gerlitz

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=4C900AF0.2040908@oracle.com \
    --to=andy.grover-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=chris.mason-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org \
    --cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@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 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.