> > 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. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
