From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ee0-x22e.google.com (mail-ee0-x22e.google.com [IPv6:2a00:1450:4013:c00::22e]) by dpdk.org (Postfix) with ESMTP id 894CF1F3 for ; Sun, 1 Sep 2013 09:01:10 +0200 (CEST) Received: by mail-ee0-f46.google.com with SMTP id c13so1700057eek.33 for ; Sun, 01 Sep 2013 00:01:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=QOhZcBLgVfm01jcex3mf21UAigQrr+05Ou2N57uGr2E=; b=NUh11EYhuucmzLq2NMUQgzqjqZatbWK3rd7HJ43appfIeqIWfkHLgbZQz7NgXCkXIo tkhMO02bA3mfQMivUnvGkwb7DsAXlbWg1GBVyL4S6J9UZObTj4qYCmRwTWhVCxZ6rHRK OZ8QmebpBSJDio1b1p5NEBRLp0ckHF5vHubRZ0O+xCDCBt0UvhLzuK3t5zyTc8ywh1XQ 9Wuk2WiiQcMYe5DxQrwKZpLjAjlATVwJ6Ww2x4NSWmG4cHP9yHkT469NeWVv9tkyHbIJ YEJaGXVzSSENXcO7EYuTwXf/emUgRTXBKLHl4Vh4qwlYunrGVXyCx4aFn6VuKqAYQx+N hYkQ== MIME-Version: 1.0 X-Received: by 10.14.126.73 with SMTP id a49mr1058193eei.48.1378018903342; Sun, 01 Sep 2013 00:01:43 -0700 (PDT) Received: by 10.223.101.143 with HTTP; Sun, 1 Sep 2013 00:01:43 -0700 (PDT) Date: Sun, 1 Sep 2013 02:01:43 -0500 Message-ID: From: Nulik Nol To: dev@dpdk.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [dpdk-dev] About interrupts and packet loss 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, 01 Sep 2013 07:01:10 -0000 Hi, I have read in a pdf document about DPDK that the driver that comes within the DPDK distribution was modified to disable interrupt handling. This explains why DPDK is so fast. However , this means the app in user space must constantly watch for new packets, so the CPU load average will be almost 100% all the time, correct? Well, then what happens if the app executes a busy process and at that time all RX rings get filled, will the incoming network traffic be lost? Thanks in advance Nulik