Chris so far we have put filtering only in "old" DNA. I still need to update all the DNA drivers, and then eventually back port the filters. Please allow us some more time as drivers changed quite a bit.
Luca On Nov 3, 2011, at 7:29 PM, Chris Wakelin wrote: > Thanks Luca for the driver update! > > However, I've been looking at the hardware filtering options and found > that my card isn't being recognised as supporting it. > > Here's dmesg after > > insmod pf_ring.ko enable_debug=1 transparent_mode=2 > insmod ixgbe DCA=2,2 FdirMode=2,2 > >> [638314.817923] Intel(R) 10 Gigabit PCI Express Network Driver - version >> 3.6.7-NAPI >> [638314.817928] Copyright (c) 1999-2011 Intel Corporation. >> [638314.817981] ixgbe 0000:0c:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ >> 16 >> [638314.817999] ixgbe 0000:0c:00.0: setting latency timer to 64 >> [638314.970260] ixgbe: Direct Cache Access (DCA) set to 2 >> [638314.970263] ixgbe: 0000:0c:00.0: ixgbe_check_options: DCA enabled for rx >> data >> [638314.970266] ixgbe: Flow Director filtering mode set to 2 >> [638314.970268] ixgbe: 0000:0c:00.0: ixgbe_check_options: Flow Director >> perfect filtering enabled >> [638314.970271] ixgbe: 0000:0c:00.0: ixgbe_check_options: FCoE Offload >> feature enabled >> [638314.992424] ixgbe 0000:0c:00.0: irq 114 for MSI/MSI-X >> [638314.992431] ixgbe 0000:0c:00.0: irq 115 for MSI/MSI-X >> [638314.992437] ixgbe 0000:0c:00.0: irq 116 for MSI/MSI-X >> [638314.992443] ixgbe 0000:0c:00.0: irq 117 for MSI/MSI-X >> [638314.992449] ixgbe 0000:0c:00.0: irq 118 for MSI/MSI-X >> [638314.992456] ixgbe 0000:0c:00.0: irq 119 for MSI/MSI-X >> [638314.992462] ixgbe 0000:0c:00.0: irq 120 for MSI/MSI-X >> [638314.992468] ixgbe 0000:0c:00.0: irq 121 for MSI/MSI-X >> [638314.992474] ixgbe 0000:0c:00.0: irq 122 for MSI/MSI-X >> [638314.993130] [PF_RING] packet_notifier(16) >> [638314.993132] [PF_RING] packet_notifier(eth1): unhandled message >> [msg=16][pfring_ptr= (null)] >> [638314.993884] [PF_RING] packet_notifier(5) >> [638314.993886] [PF_RING] packet_notifier(eth1) [REGISTER][pfring_ptr= >> (null)][hook=ffffffffa03b01c0] >> [638314.993892] [PF_RING] set_eeprom returned -95 >> [638314.993894] [PF_RING] Device eth1 does NOT support hardware packet >> filtering [1] >> [638314.993919] ixgbe 0000:0c:00.0: (PCI Express:2.5GT/s:Width x8) >> 00:1b:21:cd:a2:74 >> [638314.993998] ixgbe 0000:0c:00.0: eth1: MAC: 2, PHY: 8, SFP+: 3, PBA No: >> E68793-004 >> [638314.994000] ixgbe 0000:0c:00.0: eth1: Enabled Features: RxQ: 8 TxQ: 8 >> FdirPerfect RSS RSC >> [638314.995683] [PF_RING] packet_notifier(8) >> [638314.995695] ixgbe 0000:0c:00.0: eth1: Intel(R) 10 Gigabit Network >> Connection > ... > > > Am I doing something silly, or is the "eeprom" hack in the code not > working for this card? > > set_eeprom also returns "-95" for the two e1000e interfaces and 0 and > "-11" for the two bnx2 ones. > > Best Wishes, > Chris > > P.S. I'm not getting DCA warnings now, but the driver source code > suggests it (and FCoE) should be appearing in the "Enabled Features" > line, so I'm not 100% convinced! > > -- > --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- > Christopher Wakelin, [email protected] > IT Services Centre, The University of Reading, Tel: +44 (0)118 378 2908 > Whiteknights, Reading, RG6 6AF, UK Fax: +44 (0)118 975 3094 > _______________________________________________ > Ntop-misc mailing list > [email protected] > http://listgateway.unipi.it/mailman/listinfo/ntop-misc --- We can't solve problems by using the same kind of thinking we used when we created them - Albert Einstein _______________________________________________ Ntop-misc mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-misc
