From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Laurence Oberman <loberman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Bart Van Assche <Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org>,
"leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
<dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org"
<swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>,
"markb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org"
<markb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH rdma-next v7 0/8] RDMA resource tracking
Date: Tue, 30 Jan 2018 14:40:42 -0700 [thread overview]
Message-ID: <20180130214042.GL17053@ziepe.ca> (raw)
In-Reply-To: <1517347999.15224.2.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On Tue, Jan 30, 2018 at 04:33:19PM -0500, Laurence Oberman wrote:
> > > Since you didn't report the ib_alloc_mr() print it can't be the
> > > other
> > > ENOMEM case?
> > >
> > > Hard to see how that interesects with resource tracking.. Are you
> > > thinking memory corruption?
> >
> > Hello Jason,
> >
> > I don't see any reason to suspect memory corruption. kmemleak isn't
> > reporting
> > any memory leaks. Maybe memory fragmentation has increased?
> >
> > Thanks,
> >
> > Bart
>
> Hi Bart,
>
> Can I take your tree and see if this fails for me too,
> Your last tree was fine, so did not have this latest stuff.
> Can I just pull to what I have
Try what we are about to send as a PR:
git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git
branch wip/for-linus-merged
https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=wip/for-linus-merged
No guess why a kzalloc will fail. How much is it asking for anyhow?
Did the size get out of control for some reason?
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
prev parent reply other threads:[~2018-01-30 21:40 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-28 9:17 [PATCH rdma-next v7 0/8] RDMA resource tracking Leon Romanovsky
[not found] ` <20180128091725.13103-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-28 9:17 ` [PATCH rdma-next v7 1/8] RDMA/core: Print caller name instead of function name Leon Romanovsky
2018-01-28 9:17 ` [PATCH rdma-next v7 2/8] RDMA/core: Save kernel caller name in PD and CQ objects Leon Romanovsky
2018-01-28 9:17 ` [PATCH rdma-next v7 3/8] RDMA/restrack: Add general infrastructure to track RDMA resources Leon Romanovsky
[not found] ` <20180128091725.13103-4-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-28 21:03 ` Jason Gunthorpe
[not found] ` <20180128210350.GJ23869-uk2M96/98Pc@public.gmane.org>
2018-01-29 5:37 ` Leon Romanovsky
2018-01-28 9:17 ` [PATCH rdma-next v7 4/8] RDMA/core: Add resource tracking for create and destroy QPs Leon Romanovsky
2018-01-28 9:17 ` [PATCH rdma-next v7 5/8] RDMA/core: Add resource tracking for create and destroy CQs Leon Romanovsky
2018-01-28 9:17 ` [PATCH rdma-next v7 6/8] RDMA/core: Add resource tracking for create and destroy PDs Leon Romanovsky
[not found] ` <20180128091725.13103-7-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-28 20:48 ` Jason Gunthorpe
[not found] ` <20180128204858.GI23869-uk2M96/98Pc@public.gmane.org>
2018-01-29 5:14 ` Leon Romanovsky
2018-01-28 9:17 ` [PATCH rdma-next v7 7/8] RDMA/nldev: Provide global resource utilization Leon Romanovsky
[not found] ` <20180128091725.13103-8-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2018-01-28 20:45 ` Jason Gunthorpe
[not found] ` <20180128204513.GH23869-uk2M96/98Pc@public.gmane.org>
2018-01-29 5:09 ` Leon Romanovsky
[not found] ` <20180129050922.GA1393-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-29 17:59 ` Jason Gunthorpe
2018-01-28 9:17 ` [PATCH rdma-next v7 8/8] RDMA/nldev: Provide detailed QP information Leon Romanovsky
2018-01-28 21:05 ` [PATCH rdma-next v7 0/8] RDMA resource tracking Jason Gunthorpe
[not found] ` <20180128210520.GK23869-uk2M96/98Pc@public.gmane.org>
2018-01-29 5:39 ` Leon Romanovsky
2018-01-29 20:11 ` Doug Ledford
[not found] ` <1517256713.27592.241.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-30 3:34 ` Jason Gunthorpe
[not found] ` <20180130033436.GA17053-uk2M96/98Pc@public.gmane.org>
2018-01-30 9:16 ` Leon Romanovsky
[not found] ` <20180130091654.GD2055-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-30 15:21 ` Steve Wise
2018-01-30 15:56 ` Jason Gunthorpe
[not found] ` <20180130155643.GC17053-uk2M96/98Pc@public.gmane.org>
2018-01-30 16:16 ` Steve Wise
2018-01-30 16:33 ` Jason Gunthorpe
[not found] ` <20180130163330.GE17053-uk2M96/98Pc@public.gmane.org>
2018-01-30 19:07 ` Bart Van Assche
[not found] ` <1517339252.2589.34.camel-Sjgp3cTcYWE@public.gmane.org>
2018-01-30 19:46 ` Jason Gunthorpe
[not found] ` <20180130194639.GJ17053-uk2M96/98Pc@public.gmane.org>
2018-01-30 20:42 ` Bart Van Assche
[not found] ` <1517344962.2589.39.camel-Sjgp3cTcYWE@public.gmane.org>
2018-01-30 20:48 ` Jason Gunthorpe
[not found] ` <20180130204840.GK17053-uk2M96/98Pc@public.gmane.org>
2018-01-30 21:22 ` Bart Van Assche
[not found] ` <1517347322.2589.58.camel-Sjgp3cTcYWE@public.gmane.org>
2018-01-30 21:33 ` Laurence Oberman
[not found] ` <1517347999.15224.2.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-30 21:40 ` Bart Van Assche
[not found] ` <1517348412.2589.60.camel-Sjgp3cTcYWE@public.gmane.org>
2018-01-30 21:42 ` Jason Gunthorpe
[not found] ` <20180130214227.GM17053-uk2M96/98Pc@public.gmane.org>
2018-01-30 21:47 ` Bart Van Assche
[not found] ` <1517348867.2589.63.camel-Sjgp3cTcYWE@public.gmane.org>
2018-01-30 22:02 ` Jason Gunthorpe
[not found] ` <20180130220233.GN17053-uk2M96/98Pc@public.gmane.org>
2018-01-30 22:10 ` Bart Van Assche
2018-01-30 21:40 ` Jason Gunthorpe [this message]
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=20180130214042.GL17053@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=Bart.VanAssche-Sjgp3cTcYWE@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=loberman-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=markb-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@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.