public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale•com>
To: Laurentiu Tudor <b10716@freescale•com>
Cc: Mihai Caraman <mihai.caraman@freescale•com>,
	Laurentiu Tudor <Laurentiu.Tudor@freescale•com>,
	linuxppc-dev <linuxppc-dev@lists•ozlabs.org>
Subject: Re: [PATCH 4/4] powerpc/fsl_msi: spread msi ints across different MSIRs
Date: Tue, 19 Aug 2014 19:20:32 -0500	[thread overview]
Message-ID: <1408494032.4058.61.camel@snotra.buserror.net> (raw)
In-Reply-To: <53F33413.3050009@freescale.com>

A couple nits that don't necessarily warrant a respin:

On Tue, 2014-08-19 at 14:25 +0300, Laurentiu Tudor wrote:
> Allocate msis such that each time a new
> interrupt is requested, the SRS (MSIR
> register select) to be used is allocated
> in a round-robin fashion.
> The end result is that the msi interrupts
> will be spread across distinct MSIRs with
> the main benefit that now users can set
> affinity to each msi int through the mpic
> irq backing up the MSIR register.
> This is achieved with the help of a newly
> introduced msi bitmap api that allows
> specifying the starting point when
> searching for a free msi interrupt.

Please wrap at around 60-70 columns.

> +			} else {
> +				off = (atomic_inc_return(&msi_data->msi_alloc_cnt) %
> +					msi_data->msir_num);
> +				off *= (1 << msi_data->srs_shift);

This is an unusual way to write "off <<= msi->data->srs_shift"...

-Scott

      reply	other threads:[~2014-08-20  0:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 11:25 [PATCH 4/4] powerpc/fsl_msi: spread msi ints across different MSIRs Laurentiu Tudor
2014-08-20  0:20 ` Scott Wood [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=1408494032.4058.61.camel@snotra.buserror.net \
    --to=scottwood@freescale$(echo .)com \
    --cc=Laurentiu.Tudor@freescale$(echo .)com \
    --cc=b10716@freescale$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mihai.caraman@freescale$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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