From: Max Krasnyansky <maxk@qualcomm.com>
To: Paul Jackson <pj@sgi.com>
Cc: hch@infradead.org, mingo@elte.hu, a.p.zijlstra@chello.nl,
linux-kernel@vger.kernel.org, menage@google.com
Subject: Re: [PATCH 1/2] cpuset: cpuset irq affinities
Date: Tue, 11 Mar 2008 12:50:32 -0700 [thread overview]
Message-ID: <47D6E288.4010601@qualcomm.com> (raw)
In-Reply-To: <20080311135821.99a419e2.pj@sgi.com>
Paul Jackson wrote:
> Max wrote:
>> Sorry I missed your comment. Actually I just looked at the archive of the
>> original thread and I do not see any comments from you. Were they maybe sent
>> in private to Peter Z ? Can you please resend them ?
>
> I suspect Christoph is referring to a comment he made on lkml, at:
>
> http://lkml.org/lkml/2008/3/2/3
Got it. The comment was
> linux/irq.h must not be included in generic code, it's actually more
> and asm-generic/hw_irq.h. Please restructure the code so that the
> cpuset code calls into an arch interface which will then be implemented
> by arch code (which in most cases will be genirq, the other can be left
> stubbed out for now)
I'm not sure I agree with that though. We need access to irq_set_affinity()
from the cpuset code. It does not seem to make sense to call some arch
specific code if that functionality is provided by the generic layer.
Also note that IRQ functionality in the cpuset is ifdefed by the
CONFIG_GENERIC_HARDIRQS, so that we guarantied to have access to the generic code.
In addition to the irq_set_affinity we need irq_iterator() which is added by
the patch. Which again is generic.
So the question is why would we want to call into an arch interface if we can
call the generic one directly ?
Max
next prev parent reply other threads:[~2008-03-11 19:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 5:57 [PATCH 0/2] cpusets: support for irqs maxk
2008-03-11 5:57 ` [PATCH 1/2] cpuset: cpuset irq affinities maxk
2008-03-11 5:57 ` [PATCH 2/2] cpusets: Improved irq affinity handling maxk
2008-03-11 6:35 ` [PATCH 1/2] cpuset: cpuset irq affinities Christoph Hellwig
2008-03-11 17:05 ` Max Krasnyansky
2008-03-11 18:58 ` Paul Jackson
2008-03-11 19:50 ` Max Krasnyansky [this message]
2008-03-11 6:57 ` Paul Jackson
2008-03-11 17:25 ` Max Krasnyansky
2008-03-11 19:08 ` Paul Jackson
2008-03-11 21:31 ` Max Krasnyansky
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=47D6E288.4010601@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=pj@sgi.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.