From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id C6F855697 for ; Fri, 15 May 2015 15:14:10 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga102.fm.intel.com with ESMTP; 15 May 2015 06:14:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,433,1427785200"; d="scan'208";a="571867879" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.79]) by orsmga003.jf.intel.com with SMTP; 15 May 2015 06:14:03 -0700 Received: by (sSMTP sendmail emulation); Fri, 15 May 2015 14:14:00 +0025 Date: Fri, 15 May 2015 14:14:00 +0100 From: Bruce Richardson To: Thomas Monjalon Message-ID: <20150515131400.GC5884@bricha3-MOBL3> References: <1431012951-6423-1-git-send-email-bruce.richardson@intel.com> <20150513134048.GA13080@bricha3-MOBL3> <20150513155831.GA13524@bricha3-MOBL3> <1673093.vQ9JViuheI@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1673093.vQ9JViuheI@xps13> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH 00/19] Move PMDs to drivers directory 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: Fri, 15 May 2015 13:14:11 -0000 On Fri, May 15, 2015 at 02:54:50PM +0200, Thomas Monjalon wrote: > 2015-05-13 16:58, Bruce Richardson: > > On Wed, May 13, 2015 at 02:40:48PM +0100, Bruce Richardson wrote: > > > On Wed, May 13, 2015 at 03:33:27PM +0200, Thomas Monjalon wrote: > > > > 2015-05-13 11:01, Bruce Richardson: > > > > > On Tue, May 12, 2015 at 09:30:45PM +0200, Thomas Monjalon wrote: > > > > >> 2015-05-12 19:04, Bruce Richardson: > > > > >>> drivers/e1000/e1000/e1000_hw.h | 1026 ++++ > > > > >> > > > > >> As explained in a previous comment, > > > > >> http://dpdk.org/ml/archives/dev/2015-May/017509.html > > > > >> I think this path would be better: > > > > >> drivers/net/e1000/base/e1000_hw.h > > > > > > > > > > Two reasons why I didn't create the "net" subfolder: > > > > > 1. I initally forgot to consider it :-( > > > > > 2. While we may at some future point have other device driver types, are we really > > > > > needing to start categorising PMDs at this point? > > > > > > > > > > As for the base driver part, I was viewing that as a something that should be > > > > > a separate patch set, since it's unrelated to moving things to the drivers > > > > > subdir. > > > > > > > > I understand your points and I partially agree. > > > > However, file moves may be perturbing because it change habits > > > > and may complicate a bit the git history browsing. > > > > So I think it's better to minimize such moves and do altogether. > > > > > > > Ok. I'll see about renaming the base code directories as part of the overall > > > move process [Unless there are objections from any of the driver maintainers]. > > > > > > As for drivers vs drivers/net, I suppose there is no real difference in what > > > the path actually is, so I can make that change too. However, I still think I > > > prefer the shorter path. Anyone else any opinions on this [before I start > > > reworking this again]? > > > > A further thought on the splitting up of drivers. What about devices which provide > > more than one type of offload, how would the PMD for such a device be classified? > > Other projects (e.g. Linux) would have the same classification problem. > How do they solve it? Is it possible to split code in different directories > or different drivers? > No idea, possibly some of the resident linux kernel experts on-list can inform us. However, this is likely a solved problem, so I'm going to rework the patchset to use drivers/net for now, and thereby allow future-proofing for other device types. /Bruce