From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: Tziporet Koren <tziporet-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mode connected infiniband
Date: Wed, 20 Jan 2010 12:29:49 -0700 [thread overview]
Message-ID: <20100120192949.GI16490@obsidianresearch.com> (raw)
In-Reply-To: <adar5pl37ky.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
On Tue, Jan 19, 2010 at 05:09:49PM -0800, Roland Dreier wrote:
>
> > The last time I tried to use it the kernel began reporting lots of
> > OOM events (2.6.30 stock). I thought this was well known because CM
> > mode uses high order allocations??
>
> That's not well-known to me. What's the backtrace for those high-order
> allocations? I thought the CM code was careful to allocate receive
> buffers using page-size fragments but maybe there's some other path (skb
> rings, QP/CQ structures?) that does a higher-order alloc.
Hmm, I'll keep an eye out then. I've seen it several times in very
different systems, usually just turn CM mode off and it goes
away. Unfortunately I have no systems like that now and I didn't keep
the traces... The traces did have ipoib function calls.
Jason
--
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-20 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-14 8:11 mode connected infiniband Nico
[not found] ` <8fd3bb681001140011k5ec9492eg19b59b110e45a2b5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-14 16:06 ` Frank Leers
2010-01-14 17:22 ` Roland Dreier
[not found] ` <adabpgwmwiw.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-01-16 13:42 ` Nico
2010-01-17 8:03 ` Tziporet Koren
[not found] ` <4B52C456.5030501-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>
2010-01-18 2:56 ` Jason Gunthorpe
[not found] ` <20100118025626.GG9059-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-01-20 1:09 ` Roland Dreier
[not found] ` <ab66a8181001200002n120af0e7m3733b42a945dc06b@mail.gmail.com>
[not found] ` <ab66a8181001200002n120af0e7m3733b42a945dc06b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-20 19:21 ` Roland Dreier
[not found] ` <adar5pl37ky.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2010-01-20 19:29 ` Jason Gunthorpe [this message]
2010-01-20 1:10 ` 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=20100120192949.GI16490@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org \
--cc=tziporet-VPRAkNaXOzVS1MOuV/RT9w@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