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-prev] [day] [month] [year] [list]
Date:	Mon, 23 Dec 2013 22:28:17 +0000
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Amir Vadai <amirv@...lanox.com>
CC:	Eugenia Emantayev <eugenia@...lanox.com>,
	netdev <netdev@...r.kernel.org>
Subject: Re: Definition of the term rx/tx/combined channel

On Sun, 2013-12-22 at 17:06 +0200, Amir Vadai wrote:
> Hi Ben,
> 
> I'm trying to understand the exact definition of the term channel.
> 
> According to ethtool: A channel is an IRQ and the set of queues that can
> trigger that IRQ.
> 
> In our driver (Mellanox's Connect-X), we have an IRQ's, rx rings and tx
> rings.
> 
> Usually we have one IRQ per rx ring, but if system resources are
> limited, those numbers could be different.
> tx rings are sharing the same IRQ's assigned by rx rings (for
> completions), but many tx rings could share the same IRQ.
> 
> Is the rx channels == number of rx rings, and same for tx?
> How is this related to the number of IRQ's?

If an IRQ is triggered by completions from both RX and TX rings then
that's a combined channel.

Do you want to make the number of TX rings per IRQ configurable through
ethtool?

> Should we show other IRQ's we use for async events from the HW, as 'other'?

If they are only used for those events and not also for completions,
then yes.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ