From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cstnet.cn (smtp23.cstnet.cn [159.226.251.23]) by dpdk.org (Postfix) with ESMTP id F2A73A10 for ; Sun, 26 Jul 2015 08:42:39 +0200 (CEST) Received: from [127.0.0.1] (unknown [45.62.110.9]) by app3 (Coremail) with SMTP id SQCowJDLMu9YgbRVNmgaAA--.19186S3; Sun, 26 Jul 2015 14:42:36 +0800 (CST) From: he peng Message-Id: Date: Sun, 26 Jul 2015 14:42:31 +0800 To: dev@dpdk.org, sabu2kurian@gmail.com, bruce.richardson@intel.com Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) X-Mailer: Apple Mail (2.2098) X-CM-TRANSID: SQCowJDLMu9YgbRVNmgaAA--.19186S3 X-Coremail-Antispam: 1UD129KBjvJXoW7uF1fXFWDGF1UAFWkAw4UCFg_yoW8KrW8pF s3J34xJr1kJryxJw4UAw1UXryUAr4kC3y5G348J34vyw4DCFyFyryUKrW8KF9rGFy8A3W2 qr1DKryUAFWUZrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUqFb7Iv0xC_Kw4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2z4x0Y4vE2Ix0cI8IcVAFwI0_Gr0_Xr1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI0_Gr0_ Cr1l84ACjcxK6I8E87Iv67AKxVWxJr0_GcWl84ACjcxK6I8E87Iv6xkF7I0E14v26F4UJV W0owAS0I0E0xvYzxvE52x082IY62kv0487McIj6xIIjxv20xvE14v26r1j6r18McIj6I8E 87Iv67AKxVWUJVW8JwAm72CE4IkC6x0Yz7v_Jr0_Gr1lF7xvr2IYc2Ij64vIr41lF7xvr2 IYc2Ij64vIr40E4x8a64kEw24lc2xSY4AK6IIF6r47MxAIw28IcxkI7VAKI48JMI8I3I0E 5I8CrVAFwI0_JrI_JrWlx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUXV WUAwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x0267AKxVWUJVW8 JwCI42IY6xAIw20EY4v20xvaj40_WFyUJVCq3wCI42IY6I8E87Iv67AKxVWUJVW8JwCI42 IY6I8E87Iv6xkF7I0E14v26r1j6r4UYxBIdaVFxhVjvjDU0xZFpf9x0zRUUUUUUUUU= X-CM-SenderInfo: pkhsv0nj6lu3wodfhubq/ Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] Intel I350 fails to work with DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jul 2015 06:42:41 -0000 Hi, Sabu and Bruce: I saw your post in the mailing list about I350 fails to send = packets, however it is posted about one year ago.=20 Now we have encountered the same issue.=20 We are now building a forwarding device which forwards packets = between 2 I350 ports, and we observe that the program will=20 transmit a few hundreds of packets then the I350 seems freeze: it fails = to send all the packets. Sometimes one port and sometimes both ports = fail=20 to send any packets. After some code investigation, we find out that the program fails = to send packets because there is one packet descriptor=A1=AFs DD bit is = not set by the hardware DMA, so the driver thinks that the TX ring is = full then it drops all the packets. Below is the code (eth_igb_xmit_pkts = in igb_rxtx.c) where the rte_eth_tx_burst returns: if (! (txr[tx_end].wb.status & E1000_TXD_STAT_DD)) { if (nb_tx =3D=3D 0) return (0); goto end_of_tx; } We have checked the corresponding sw_ring[tx_end]->mbuf , the packet = content seems fine, it is a normal 64 bytes packet. Our code is quite = simple, just adding/removing tunnel tags in the packets. The total = length of packet tags is 28 bytes. Maybe it is because there is some = align requirements on the memory addresses where the packet content = begins? I do not know. Below is the output of l2fwd. /home/dpdk-1.8.0/examples/l2fwd/build/l2fwd -c 0x6 -n 2 -- -p 0x6 Port statistics =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Statistics for port 1 ------------------------------ Packets sent: 13585277499 Packets received: 6792638878 Packets dropped: 0 Statistics for port 2 ------------------------------ Packets sent: 649 Packets received: 13585277549 Packets dropped: 6792638229 Aggregate statistics =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Total packets sent: 13585278180 Total packets received: 20377916457 Total packets dropped: 6792638229 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D After the card goes freeze, we run the l2fwd and find out that it = encounters the same issues. The program forward only around 600 packets, = then it begins to drop all the other packets. We now start to doubt this = is a problem of the network card, but we are not sure that if it is = because the hardware has already been messed up, after so many times of = restarting the programs and testing. =20 Any help is appreciated ! Thanks.=20 =20=