From: Steve Wise <swise@opengridcomputing.com>
To: Caitlin Bestler <caitlinb@broadcom.com>
Cc: Bob Sharp <bsharp@NetEffect.com>,
openib-general <openib-general@openib.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: RE: [openib-general] [PATCH v2 1/7] AMSO1100 Low Level Driver.
Date: Thu, 15 Jun 2006 16:58:29 -0500 [thread overview]
Message-ID: <1150408709.6612.16.camel@stevo-desktop> (raw)
In-Reply-To: <54AD0F12E08D1541B826BE97C98F99F15767E3@NT-SJCA-0751.brcm.ad.broadcom.com>
> > Now that I've looked more into this, I'm not sure there's a
> > simple way for the IWCM to copy the pdata on the upcall.
> > Currently, the IWCM's event upcall, cm_event_handler(),
> > simply queues the work for processing on a workqueue thread.
> > So there's no per-event logic at all there.
> > Lemme think on this more. Stay tuned.
> >
> > Either way, the amso driver has a memory leak...
> >
>
> Having the IWCM copy the pdata during the upcall also leaves
> the greatest flexibility for the driver on how/where the pdata
> is captured. The IWCM has to deal with user-mode, indefinite
> delays waiting for a response and user-mode processes that die
> while holding a connection request. So it makes sense for that
> layer to do the allocating and copying.
I've already coded and test this. The IWCM will copy the pdata...
Steve.
next prev parent reply other threads:[~2006-06-15 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-15 21:45 [openib-general] [PATCH v2 1/7] AMSO1100 Low Level Driver Caitlin Bestler
2006-06-15 21:58 ` Steve Wise [this message]
[not found] <5E701717F2B2ED4EA60F87C8AA57B7CC05D4E2D8@venom2>
2006-06-15 13:41 ` Steve Wise
2006-06-15 14:03 ` Steve Wise
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=1150408709.6612.16.camel@stevo-desktop \
--to=swise@opengridcomputing.com \
--cc=bsharp@NetEffect.com \
--cc=caitlinb@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.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