From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kumar Gala Subject: Re: [PATCH 1/9] [I/OAT] DMA memcpy subsystem Date: Fri, 31 Mar 2006 14:06:29 -0600 Message-ID: References: <20060329225505.25585.30392.stgit@gitlost.site> <351C5BDA-D7E3-4257-B07E-ABDDCF254954@kernel.crashing.org> <200603311026.33391.netdev@axxeo.de> Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit Cc: "Ingo Oeser" , "Chris Leech" , linux-kernel@vger.kernel.org, netdev@vger.kernel.org Return-path: In-Reply-To: To: "Andrew Grover" Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Mar 31, 2006, at 2:04 PM, Andrew Grover wrote: > On 3/31/06, Ingo Oeser wrote: >> Kumar Gala wrote: >>> Fair, but wouldn't it be better to have the association per client. >>> >>> Maybe leave the one as a summary and have a dir per client with >>> similar stats that are for each client and add a per channel summary >>> at the top level as well. >> Such level of detail really belongs to debugging, IMHO. > [snip] > > If we implemented more stats then yes debugfs sounds like it might be > the way to go. > >> BTW: What is the actual frequency, at which such counters >> will be incremented? > > Currently the code updates these variables (kept per cpu) every time a > copy is queued. See include/linux/dmaengine.h. Might it be better to update when the transfer is done incase of an error? - kumar