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  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]
Date:	Mon, 2 Jul 2007 12:00:29 -0700
From:	"Veeraiyan, Ayyappan" <ayyappan.veeraiyan@...el.com>
To:	"Jeff Garzik" <jeff@...zik.org>
Cc:	<netdev@...r.kernel.org>,
	"Kok, Auke-jan H" <auke-jan.h.kok@...el.com>,
	<arjan@...ux.intel.com>, <akpm@...ux-foundation.org>
Subject: RE: [PATCH] ixgbe: Introduce new 10GbE driver for Intel 82598 based PCI	Express adapters...

On 7/2/07, Jeff Garzik <jeff@...zik.org> wrote:
> Ayyappan Veeraiyan wrote:
> > +#define IXGBE_TX_FLAGS_VLAN_MASK     0xffff0000
> > +#define IXGBE_TX_FLAGS_VLAN_SHIFT    16
> 
> defining bits using the form "(1 << n)" is preferred.  Makes it easier
> to read, by eliminating the requirement of the human brain to decode
hex
> into bit numbers.
> 
> 

Ok.

> > +             struct net_device netdev;
> > +     };
> 
> Embedded a struct net_device into your ring?  How can I put this?
> 
> Wrong, wrong.  Wrong, wrong, wrong.  Wrong.
> 

Agreed. 
Fake netdevs are needed for doing the multiple Rx queues in NAPI mode.
We are thinking to solve in 2 ways. Having netdev pointer in ring
structure or having an array of netdev pointers in ixgbe_adatper struct
which would be visible to all rings.

> > +
> > +     char name[IFNAMSIZ + 5];
> 
> The interface name should not be stored by your ring structure
>

Yes, I agree and also (pointed out by someone before) this would break
if the user changes the interface name..
But, having the "cause" in the MSIX vector name really helps in
debugging and helps the user also. 

I think the below output is much better

[root@...apsz src]# cat /proc/interrupts | grep eth0
214:          0          0   PCI-MSI-edge      eth0-lsc
215:      11763          4   PCI-MSI-edge      eth0-rx7
216:          0          0   PCI-MSI-edge      eth0-rx6
217:      77324          0   PCI-MSI-edge      eth0-rx5
218:          0          0   PCI-MSI-edge      eth0-rx4
219:      52911          0   PCI-MSI-edge      eth0-rx3
220:      80271          0   PCI-MSI-edge      eth0-rx2
221:      80244          6   PCI-MSI-edge      eth0-rx1
222:         12          0   PCI-MSI-edge      eth0-rx0
223:     124870      28543   PCI-MSI-edge      eth0-tx0

Compared to 

[root@...apsz src]# cat /proc/interrupts | grep eth0
214:          0          0   PCI-MSI-edge      eth0
215:      11763          4   PCI-MSI-edge      eth0
216:          0          0   PCI-MSI-edge      eth0
217:      77324          0   PCI-MSI-edge      eth0
218:          0          0   PCI-MSI-edge      eth0
219:      52911          0   PCI-MSI-edge      eth0
220:      80271          0   PCI-MSI-edge      eth0
221:      80244          6   PCI-MSI-edge      eth0
222:         12          0   PCI-MSI-edge      eth0
223:     124900      28543   PCI-MSI-edge      eth0

Since we wanted to distinguish the various MSIX vectors in
/proc/interrupts and since request_irq expects memory for name to be
allocated somewhere, I added this part of the ring struct.

> 
> Kill io_base and stop setting netdev->base_addr

In my latest internal version, I already removed the io_base member (and
couple more from ixgbe_adapter) but still setting the netdev->base_addr.
I will remove that also..

> > +     struct ixgbe_hw_stats stats;
> > +     char lsc_name[IFNAMSIZ + 5];
> 
> delete lsc_name and use netdev name directly in request_irq()
> 

Please see the response for the name member of ring structure.
 
> 
> Will review more after you fix these problems.
> 

Thanks for the feedback. I will post another version shortly (except the
feature flags change and the ring struct name members) which fixes my
previous TODO list and also most of Francois comments..

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