[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080919.131402.157398113.davem@davemloft.net>
Date: Fri, 19 Sep 2008 13:14:02 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: matthew@....cx
Cc: netdev@...r.kernel.org, arjan@...radead.org
Subject: Re: multiqueue interrupts...
From: Matthew Wilcox <matthew@....cx>
Date: Fri, 19 Sep 2008 12:18:41 -0600
> On Thu, Sep 18, 2008 at 7:38 PM, David Miller wrote:
> > During kernel summit I was speaking with Arjan van de Ven
> > about irqbalanced and networking card multiqueue interrupts.
> >
> > In order for irqbalanaced to make smart decisions, what needs to
> > happen in drivers is that the individual interrupts need to be
> > named in such a way that he can tell by looking at /proc/interrupts
> > output that these interrupts are related.
> >
> > So on a multiqueue card with 2 RX queues and 2 TX queues we'd
> > have names like:
> >
> > eth0-rx-0
> > eth0-rx-1
> > eth0-tx-0
> > eth0-tx-1
> >
> > So let's make an effort to get this done right in 2.6.28 and meanwhile
> > Arjan can add the irqbalanced code.
>
> Instead of having magic names, how about we put something in
> /proc/irq/nnn/ that lets us tell which interrupts are connected to which
> queues?
More code for irqbalanced to write, to look for the files and
directories under there, etc. Harder to make work with simple
individual driver backports, which you know dists are going to
want to do.
That's why.
No, this new subdirectory thing isn't a good idea.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists