From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v6 0/8] Interrupt mode PMD Date: Tue, 3 Mar 2015 16:52:57 -0800 Message-ID: <20150303165257.7b7d0cd1@urahara> References: <1424710542-14637-1-git-send-email-danny.zhou@intel.com> <1425012976-10173-1-git-send-email-cunming.liang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: "dev-VfR2kkLFssw@public.gmane.org" To: David Marchand Return-path: In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On Fri, 27 Feb 2015 11:38:25 +0100 David Marchand wrote: > Ok, so after looking at this patchset, I would say this is the right direction, but still this is too limited. > The ethdev part and the vfio eventfds part look acceptable to me. > But thinking about it, I could just reuse a standard event library with the eventfds I would get from ethdev without a need for a new eal api. I would prefer that there was just an fd and a callback. An application should be able to use what ever event model or library it wants. IMHO the existing interrupt thread model is incorrectly designed and creates lots of opportunities for races because of that. Look at the effort it has to use to pass the event back to link state code.