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] [thread-next>] [day] [month] [year] [list]
Message-ID: <1328648307.8014.35.camel@nseg_linux_HP1.broadcom.com>
Date:	Tue, 7 Feb 2012 12:58:25 -0800
From:	"Michael Chan" <mchan@...adcom.com>
To:	"Ben Hutchings" <bhutchings@...arflare.com>
cc:	davem@...emloft.net, netdev@...r.kernel.org
Subject: Re: [PATCH 1/3 net-next] bnx2: Add support for ethtool
 --show-channels|--set-channels


On Tue, 2012-02-07 at 20:19 +0000, Ben Hutchings wrote:
> On Sun, 2012-02-05 at 17:24 -0800, Michael Chan wrote:
> > Allow the user to override the default number of RSS/TSS rings.
> > 
> > Signed-off-by: Michael Chan <mchan@...adcom.com>
> > ---
> >  drivers/net/ethernet/broadcom/bnx2.c |   99 ++++++++++++++++++++++++++++++---
> >  drivers/net/ethernet/broadcom/bnx2.h |    3 +
> >  2 files changed, 93 insertions(+), 9 deletions(-)
> > 
> > diff --git a/drivers/net/ethernet/broadcom/bnx2.c b/drivers/net/ethernet/broadcom/bnx2.c
> > index 0a4c540..2ab31da 100644
> > --- a/drivers/net/ethernet/broadcom/bnx2.c
> > +++ b/drivers/net/ethernet/broadcom/bnx2.c
> > @@ -6246,7 +6246,16 @@ static int
> >  bnx2_setup_int_mode(struct bnx2 *bp, int dis_msi)
> >  {
> >  	int cpus = num_online_cpus();
> > -	int msix_vecs = min(cpus + 1, RX_MAX_RINGS);
> > +	int msix_vecs;
> > +
> > +	if (!bp->num_req_rx_rings)
> > +		msix_vecs = max(cpus + 1, bp->num_req_tx_rings);
> > +	else if (!bp->num_req_tx_rings)
> > +		msix_vecs = max(cpus, bp->num_req_rx_rings);
> > +	else
> > +		msix_vecs = max(bp->num_req_rx_rings, bp->num_req_tx_rings);
> > +
> > +	msix_vecs = min(msix_vecs, RX_MAX_RINGS);
> 
> If I read this correctly, IRQs may be shared between RX and TX queues
> i.e. there may be 'combined channels'.

It is true that an IRQ can have a TX and a RX queue, but they don't both
have to be enabled.  Because of that, it is easier to treat them as
independent queues.  They are independent in all aspects except the IRQ.



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