Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1223285
| From | Scott Wood <scottwood@freescale.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [v2 04/11] soc/fsl: Introduce drivers for the DPAA QMan |
| Date | 2015-09-12 03:20 +0200 |
| Message-ID | <q7HDY-29A-5@gated-at.bofh.it> (permalink) |
| References | <pWKFc-6tA-3@gated-at.bofh.it> <q7HDY-29A-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed, Aug 12, 2015 at 04:14:50PM -0400, Roy Pledge wrote:
> +/* Lock/unlock frame queues, subject to the "LOCKED" flag. This is about
> + * inter-processor locking only. Note, FQLOCK() is always called either under a
> + * local_irq_save() or from interrupt context - hence there's no need for irq
> + * protection (and indeed, attempting to nest irq-protection doesn't work, as
> + * the "irq en/disable" machinery isn't recursive...). */
> +#define FQLOCK(fq) \
> + do { \
> + struct qman_fq *__fq478 = (fq); \
> + if (fq_isset(__fq478, QMAN_FQ_FLAG_LOCKED)) \
> + spin_lock(&__fq478->fqlock); \
> + } while (0)
> +#define FQUNLOCK(fq) \
> + do { \
> + struct qman_fq *__fq478 = (fq); \
> + if (fq_isset(__fq478, QMAN_FQ_FLAG_LOCKED)) \
> + spin_unlock(&__fq478->fqlock); \
> + } while (0)
> +
I don't see QMAN_FQ_FLAG_LOCKED set anywhere. What is the use case?
-Scott
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [v2 04/11] soc/fsl: Introduce drivers for the DPAA QMan Scott Wood <scottwood@freescale.com> - 2015-09-12 03:20 +0200 RE: [v2 04/11] soc/fsl: Introduce drivers for the DPAA QMan Roy Pledge <roy.pledge@freescale.com> - 2015-09-15 17:40 +0200
csiph-web