From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f49.google.com (mail-pb0-f49.google.com [209.85.160.49]) by dpdk.org (Postfix) with ESMTP id C9F315953 for ; Tue, 28 Jan 2014 19:11:54 +0100 (CET) Received: by mail-pb0-f49.google.com with SMTP id up15so675745pbc.36 for ; Tue, 28 Jan 2014 10:13:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=U17pg/fci54561i5jambsdNX22O+amRM9Mvpju9qrFA=; b=fnV9m+WJekvQcPQZmKCG19AnisOqeOYi41PtUKSrXuat3Bs11KqukwdTZPRWeeQYay wktaLQr6Orij8jSAnSB0uQSO00UfxIayQuW+KXAsUIZdZmrhB3FIsNumoeVQDNssstwR hKzohKxQ5TvsG3F0HCTRHIyhILvauiVNZVt4uQhld9+MMUJ13RgcLjoK6XsV4/gcotej xuLQkXt+nG2uijldR6OfbFCyWK75X4h6X+G4we9K/orm3cegC4HdoCC8fvZdfCajacXS vdPtIGsJhGpg5NJe/SGf+uvvZNsuUay3Y8BQ/dhE2jYF9HjOVwt/+d1W0c08QBEG7Vuk NEYg== X-Gm-Message-State: ALoCoQkmJLeRUYoPIgrgNl0BS5x/sgBnb4M7RXoisLAagUxnM8M7uB+qCqAusA8rNVAPuJlHgNsn X-Received: by 10.66.139.130 with SMTP id qy2mr2939786pab.73.1390932792924; Tue, 28 Jan 2014 10:13:12 -0800 (PST) Received: from nehalam.linuxnetplumber.net (static-50-53-83-51.bvtn.or.frontiernet.net. [50.53.83.51]) by mx.google.com with ESMTPSA id iq10sm44727241pbc.14.2014.01.28.10.13.12 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Tue, 28 Jan 2014 10:13:12 -0800 (PST) Date: Tue, 28 Jan 2014 10:13:09 -0800 From: Stephen Hemminger To: Thomas Monjalon Message-ID: <20140128101309.639a1b88@nehalam.linuxnetplumber.net> In-Reply-To: <201401281723.22155.thomas.monjalon@6wind.com> References: <201401271019.00293.thomas.monjalon@6wind.com> <201401281723.22155.thomas.monjalon@6wind.com> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org Subject: Re: [dpdk-dev] "No probed ethernet devices" caused by inaccurate msec_delay() 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: Tue, 28 Jan 2014 18:11:55 -0000 TSC has lots of platform related issues. It is not guaranteed sync'd across physical packages and AMD boxes have lots of problems. Why does delay_ms not just use nanosleep() and let the OS worry about it? On a related note, I have found that putting the worker (non master) threads into real time scheduling class also helps.