netdev - multiqueue interrupts...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080918.193815.175549834.davem@davemloft.net>
Date:	Thu, 18 Sep 2008 19:38:15 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	netdev@...r.kernel.org
Subject: multiqueue interrupts...

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.

I would suggest that people use something like:

	char buf[IFNAMSIZ+6];

	sprintf(buf, "%s-%s-%d",
	        netdev->name,
		(RX_INTERRUPT ? "rx" : "tx"),
		queue->index);

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.
--
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