All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Jayamohan Kallickal <jayamohank@gmail.com>
Cc: jbottomley@parallels.com, linux-scsi@vger.kernel.org,
	Jayamohan Kallickal <Jayamohan.Kallickal@emulex.com>,
	Minh Tran <minhduc.tran@emulex.com>,
	John Soni Jose <sony.john-n@emulex.com>
Subject: Re: [PATCH 2/6] be2iscsi: relinquishing control after processing 512 CQE
Date: Mon, 31 Mar 2014 00:25:11 -0500	[thread overview]
Message-ID: <5338FC37.8060906@cs.wisc.edu> (raw)
In-Reply-To: <1395938371-2149-2-git-send-email-Jayamohan.Kallickal@emulex.com>

On 03/27/2014 11:39 AM, Jayamohan Kallickal wrote:
> @@ -2323,14 +2319,33 @@ void beiscsi_process_all_cqs(struct work_struct *work)
>  
>  static int be_iopoll(struct blk_iopoll *iop, int budget)
>  {
> -	unsigned int ret;
> +	unsigned int ret, num_eq_processed;
>  	struct beiscsi_hba *phba;
>  	struct be_eq_obj *pbe_eq;
> +	struct be_eq_entry *eqe = NULL;
> +	struct be_queue_info *eq;
>  
> +	num_eq_processed = 0;
>  	pbe_eq = container_of(iop, struct be_eq_obj, iopoll);
> +	phba = pbe_eq->phba;
> +	eq = &pbe_eq->q;
> +	eqe = queue_tail_node(eq);
> +
> +	hwi_ring_eq_db(phba, eq->id, 1, num_eq_processed, 0, 1);

Is this right? num_eq_processed will be 0 above. Should this be moved
down below to after num_eq_processed has been incremented?


> +
> +	while (eqe->dw[offsetof(struct amap_eq_entry, valid) / 32]
> +			& EQE_VALID_MASK) {
> +
> +		AMAP_SET_BITS(struct amap_eq_entry, valid, eqe, 0);
> +		queue_tail_inc(eq);
> +		eqe = queue_tail_node(eq);
> +		num_eq_processed++;
> +	}


  reply	other threads:[~2014-03-31  5:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 16:39 [PATCH 1/6] be2iscsi: Fix retrieving MCCQ_WRB in non-embedded Mbox path Jayamohan Kallickal
2014-03-27 16:39 ` [PATCH 2/6] be2iscsi: relinquishing control after processing 512 CQE Jayamohan Kallickal
2014-03-31  5:25   ` Mike Christie [this message]
2014-04-03  5:02     ` Jayamohan Kallickal
2014-03-27 16:39 ` [PATCH 3/6] be2iscsi: Fix MCCQ posting for Mbx-Cmd after driver initialization is complete Jayamohan Kallickal
2014-03-28  0:45   ` Mike Christie
2014-04-03  5:02     ` Jayamohan Kallickal
2014-04-03 18:30       ` Mike Christie
2014-04-03 18:39         ` Mike Christie
2014-03-27 16:39 ` [PATCH 4/6] be2iscsi: Fix interrupt Coalescing mechanism Jayamohan Kallickal
2014-03-27 16:39 ` [PATCH 5/6] be2iscsi: Fix TCP parameters while connection offloading Jayamohan Kallickal
2014-03-31  4:53   ` Mike Christie
2014-04-03  5:02     ` Jayamohan Kallickal
2014-03-27 16:39 ` [PATCH 6/6] be2iscsi: Bump the driver version Jayamohan Kallickal
2014-03-27 16:39 ` [PATCH 0/6] be2iscsi: Update to 10.2.218.0 Jayamohan Kallickal

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=5338FC37.8060906@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=Jayamohan.Kallickal@emulex.com \
    --cc=jayamohank@gmail.com \
    --cc=jbottomley@parallels.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=minhduc.tran@emulex.com \
    --cc=sony.john-n@emulex.com \
    /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.