From: Ben Hutchings <bhutchings@solarflare.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: David Miller <davem@davemloft.net>,
Tom Herbert <therbert@google.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-net-drivers@solarflare.com
Subject: Re: [PATCH 1/2] genirq: Add IRQ affinity notifiers
Date: Fri, 14 Jan 2011 20:06:37 +0000 [thread overview]
Message-ID: <1295035597.5386.8.camel@bwh-desktop> (raw)
In-Reply-To: <alpine.LFD.2.00.1101141928210.2678@localhost6.localdomain6>
On Fri, 2011-01-14 at 20:47 +0100, Thomas Gleixner wrote:
> On Tue, 4 Jan 2011, Ben Hutchings wrote:
> > +/**
> > + * struct irq_affinity_notify - context for notification of IRQ affinity changes
> > + * @irq: Interrupt to which notification applies
> > + * @kref: Reference count, for internal use
> > + * @work: Work item, for internal use
> > + * @notify: Function to be called on change. This will be
> > + * called in process context.
> > + * @release: Function to be called on release. This will be
> > + * called in process context. Once registered, the
> > + * structure must only be freed when this function is
> > + * called or later.
> > + */
> > +struct irq_affinity_notify {
> > + unsigned int irq;
> > + struct kref kref;
> > +#if defined(CONFIG_SMP) && defined(CONFIG_GENERIC_HARDIRQS)
>
> The whole affinity thing is SMP and GENERIC_HARDIRQS only anyway, so
> what's the point of this ifdeffery ?
The intent is that code using this can be compiled even if those config
options are not set. The work_struct is not needed in that case. I
think this is probably pointless though.
> > + struct work_struct work;
> > +#endif
> > + void (*notify)(struct irq_affinity_notify *, const cpumask_t *mask);
> > + void (*release)(struct kref *ref);
> > +};
> > +
>
> > +/**
> > + * irq_set_affinity_notifier - control notification of IRQ affinity changes
> > + * @irq: Interrupt for which to enable/disable notification
> > + * @notify: Context for notification, or %NULL to disable
> > + * notification. Function pointers must be initialised;
> > + * the other fields will be initialised by this function.
> > + *
> > + * Must be called in process context. Notification may only be enabled
> > + * after the IRQ is allocated but before it is bound with request_irq()
>
> Why? And if there is that restriction, then it needs to be
> checked. But I don't see why this is necessary.
Which restriction?
> > + * and must be disabled before the IRQ is freed using free_irq().
> > + */
>
> > +#ifdef CONFIG_SMP
> > + BUG_ON(desc->affinity_notify);
>
> We should be nice here and just WARN and fixup the wreckage by
> uninstalling it.
OK.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-01-14 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 19:37 [PATCH 0/2] IRQ affinity reverse-mapping Ben Hutchings
2011-01-04 19:38 ` [PATCH 1/2] genirq: Add IRQ affinity notifiers Ben Hutchings
2011-01-14 19:47 ` Thomas Gleixner
2011-01-14 20:06 ` Ben Hutchings [this message]
2011-01-14 20:40 ` Thomas Gleixner
2011-01-04 19:39 ` [PATCH 2/2] lib: cpu_rmap: CPU affinity reverse-mapping Ben Hutchings
2011-01-04 21:17 ` Eric Dumazet
2011-01-04 21:23 ` Ben Hutchings
2011-01-04 21:45 ` Eric Dumazet
2011-01-04 22:04 ` Ben Hutchings
2011-01-04 22:19 ` Eric Dumazet
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=1295035597.5386.8.camel@bwh-desktop \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=therbert@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).