DPDK patches and discussions
 help / color / mirror / Atom feed
From: "XU Liang" <liang.xu@cinfotech.cn>
To: "Bruce Richardson" <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Should the other queues at same port work when one queue is full ?
Date: Thu, 22 Jan 2015 08:44:16 +0800	[thread overview]
Message-ID: <4fdd13ec-bc94-45d1-b467-6110bf062bbd@cinfotech.cn> (raw)
In-Reply-To: 20150119105754.GA12244@bricha3-MOBL3

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 4357 bytes --]

Thanks, I had validated the 'rx_drop_en' setting. It's worked. 
Regards,/Liang------------------------------------------------------------------From:Bruce Richardson <bruce.richardson@intel.com>Time:2015 Jan 19 (Mon) 18:58To:徐亮 <liang.xu@cinfotech.cn>Cc:dev <dev@dpdk.org>Subject:Re: [dpdk-dev] Should the other queues at same port work when one queue is full ?
On Sun, Jan 18, 2015 at 07:12:31PM +0800, XU Liang wrote:
> I configured the 82599 ports to work in multi-queue mode and flow director to assign different TCP connections to different queues. A multi-process application receive packets from queues and each process reads a queue. When I kill one process, the process's queue is full, all descriptors of the queue is used. Then I send packets to other queues, but no packet is received by other processes from other queues. And no ierrors at the port stats.  I'm not sure it's a bug or designed that way. 
> I expect that when a process exits abnormally affect only part of the connections, but now all the connections are not working properly. How can I just turn off the exception queue, so that other processes / queues work properly.

You need to turn on the "drop enable" bit in your NIC configuration to allow 
packets for full queues to be dropped, allowing other queues to continue as normal.
In DPDK this is set by the value "rx_drop_en" in the rx configuration.

In the latest DPDK tree, you can see this value being set for the symmetric mp
example application in: examples/multi_process/symmetric_mp/main.c

Regards,
/Bruce
From stephen@networkplumber.org  Thu Jan 22 01:49:34 2015
Return-Path: <stephen@networkplumber.org>
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com
 [209.85.220.44]) by dpdk.org (Postfix) with ESMTP id 7CE9D5A15
 for <dev@dpdk.org>; Thu, 22 Jan 2015 01:49:34 +0100 (CET)
Received: by mail-pa0-f44.google.com with SMTP id et14so56381537pad.3
 for <dev@dpdk.org>; Wed, 21 Jan 2015 16:49:33 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d\x1e100.net; s 130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=H8JW7fWzbM0DBli4X1upg8zgZsDDbA8KcNBeYDLxuuU=;
 bîP6qV5E/cjWU2MO8cjzjAdbTsJwWWFy3mP05loNgvofg6IZ94ZxsoHv4wNkhmRmT/
 kBHWlfPHim8umvM+KzYXVq3xyd/CTaEDpx/1qpEbrdDrwN2Tq44REtJQIjnHp6BTB5rQ
 QuYYK9AuVT4JBivrD0PUgdpNna4+BCivtXcqHiNE7ER90w5UZaz48uHzgpvPTYMNIjnQ
 GlrT8O0em8LzaGcUE/YjuyyH4FeH/9vu1lCFZ+uY8UpAwtUUqtBHz3hF2TbKoOlIxjD1
 NpE0aOYnd/PeeZOgGNByq3kRRGT0499HWVOoEquLmek/Kuu0YzVnB1MQ4L+a+u7qSSqS
 DhIQ=X-Gm-Message-State: ALoCoQltC01bkE1jUvCqzoE++kjA/XcMG8TlETacR66Eoq5divXlSieGcwNwj8T6aoD9vJdFAVbf
X-Received: by 10.68.201.1 with SMTP id jw1mr43913068pbc.167.1421887773866;
 Wed, 21 Jan 2015 16:49:33 -0800 (PST)
Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net.
 [50.53.82.155])
 by mx.google.com with ESMTPSA id ji5sm7099258pbd.22.2015.01.21.16.49.31
 (version=TLSv1.2 cipherìDHE-RSA-AES128-GCM-SHA256 bits\x128/128);
 Wed, 21 Jan 2015 16:49:33 -0800 (PST)
Date: Wed, 21 Jan 2015 16:49:25 -0800
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Message-ID: <20150121164925.10d1751c@urahara>
In-Reply-To: <5685862.aqyVHy67Ev@xps13>
References: <1418793196-17953-1-git-send-email-stephen@networkplumber.org>
 <5685862.aqyVHy67Ev@xps13>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/7] vmxnet3: driver enhancements
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2015 00:49:34 -0000

On Thu, 15 Jan 2015 12:02:11 +0100
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:

> Someone to review these patches?

Any comments from
Bruce Richardson <bruce.richardson@intel.com>

      parent reply	other threads:[~2015-01-22  0:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18 11:12 XU Liang
2015-01-19 10:57 ` Bruce Richardson
2015-01-22  0:44 ` XU Liang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4fdd13ec-bc94-45d1-b467-6110bf062bbd@cinfotech.cn \
    --to=liang.xu@cinfotech.cn \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).