lkml.org 
[lkml]   [2008]   [Mar]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 1/2] cpuset: cpuset irq affinities
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



\
 
 \ /
  Last update: 2008-03-11 20:53    [W:0.013 / U:0.164 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site