lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4CAB35A8.6080906@opengridcomputing.com>
Date:	Tue, 05 Oct 2010 09:26:48 -0500
From:	Steve Wise <swise@...ngridcomputing.com>
To:	Bernard Metzler <bmt@...ich.ibm.com>
CC:	netdev@...r.kernel.org, linux-rdma@...r.kernel.org
Subject: Re: [PATCH] SIW: Object management

On 10/05/2010 01:54 AM, Bernard Metzler wrote:

<snip>+
> +
> +/***** routines for WQE handling ***/
> +
> +/*
> + * siw_wqe_get()
> + *
> + * Get new WQE. For READ RESPONSE, take it from the free list which
> + * has a maximum size of maximum inbound READs. All other WQE are
> + * malloc'ed which creates some overhead. Consider change to
> + *
> + * 1. malloc WR only if it cannot be synchonously completed, or
> + * 2. operate own cache of reuseable WQE's.
> + *
> + * Current code trusts on malloc efficiency.
> + */
> +inline struct siw_wqe *siw_wqe_get(struct siw_qp *qp, enum siw_wr_opcode op)
> +{
> +	struct siw_wqe *wqe;
> +
> +	if (op == SIW_WR_RDMA_READ_RESP) {
> +		spin_lock(&qp->freelist_lock);
> +		if (!(list_empty(&qp->wqe_freelist))) {
> +			wqe = list_entry(qp->wqe_freelist.next,
> +					 struct siw_wqe, list);
> +			list_del(&wqe->list);
> +			spin_unlock(&qp->freelist_lock);
> +			wqe->processed = 0;
> +			dprint(DBG_OBJ|DBG_WR,
> +				"(QP%d): WQE from FreeList p: %p\n",
> +				QP_ID(qp), wqe);
> +		} else {
> +			spin_unlock(&qp->freelist_lock);
> +			wqe = NULL;
> +			dprint(DBG_ON|DBG_OBJ|DBG_WR,
> +				"(QP%d): FreeList empty!\n", QP_ID(qp));
> +		}
> +	} else {
> +		wqe = kzalloc(sizeof(struct siw_wqe), GFP_KERNEL);
> +		dprint(DBG_OBJ|DBG_WR, "(QP%d): New WQE p: %p\n",
> +			QP_ID(qp), wqe);
> +	}
>    

I think you can't allocate at GFP_KERNEL here if this is called from the 
post_ functions.  I think you might want to pre-allocate these when you 
create the QP...


Steve.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ