Return-path: Received: from mga01.intel.com ([192.55.52.88]:36771 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755884Ab3AICls (ORCPT ); Tue, 8 Jan 2013 21:41:48 -0500 Date: Wed, 9 Jan 2013 10:42:26 +0800 From: Yuanhan Liu To: Dmitry Torokhov Cc: linux-kernel@vger.kernel.org, Stefani Seibold , Andrew Morton , linux-omap@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, platform-driver-x86@vger.kernel.org, linux-input@vger.kernel.org, linux-iio@vger.kernel.org, linux-rdma@vger.kernel.org, linux-media@vger.kernel.org, linux-mmc@vger.kernel.org, linux-mtd@lists.infradead.org, libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-pci@vger.kernel.org, open-iscsi@googlegroups.com, linux-scsi@vger.kernel.org, devel@driverdev.osuosl.org, linux-serial@vger.kernel.org, linux-usb@vger.kernel.org, linux-mm@kvack.org, dccp@vger.kernel.org, linux-sctp@vger.kernel.org Subject: Re: [PATCH 5/5] kfifo: log based kfifo API Message-ID: <20130109024226.GD304@yliu-dev.sh.intel.com> (sfid-20130109_034205_590622_E79688A6) References: <1357657073-27352-1-git-send-email-yuanhan.liu@linux.intel.com> <1357657073-27352-6-git-send-email-yuanhan.liu@linux.intel.com> <20130108181645.GA7972@core.coreip.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20130108181645.GA7972@core.coreip.homeip.net> Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, Jan 08, 2013 at 10:16:46AM -0800, Dmitry Torokhov wrote: > Hi Yuanhan, > > On Tue, Jan 08, 2013 at 10:57:53PM +0800, Yuanhan Liu wrote: > > The current kfifo API take the kfifo size as input, while it rounds > > _down_ the size to power of 2 at __kfifo_alloc. This may introduce > > potential issue. > > > > Take the code at drivers/hid/hid-logitech-dj.c as example: > > > > if (kfifo_alloc(&djrcv_dev->notif_fifo, > > DJ_MAX_NUMBER_NOTIFICATIONS * sizeof(struct dj_report), > > GFP_KERNEL)) { > > > > Where, DJ_MAX_NUMBER_NOTIFICATIONS is 8, and sizeo of(struct dj_report) > > is 15. > > > > Which means it wants to allocate a kfifo buffer which can store 8 > > dj_report entries at once. The expected kfifo buffer size would be > > 8 * 15 = 120 then. While, in the end, __kfifo_alloc will turn the > > size to rounddown_power_of_2(120) = 64, and then allocate a buf > > with 64 bytes, which I don't think this is the original author want. > > > > With the new log API, we can do like following: > > > > int kfifo_size_order = order_base_2(DJ_MAX_NUMBER_NOTIFICATIONS * > > sizeof(struct dj_report)); > > > > if (kfifo_alloc(&djrcv_dev->notif_fifo, kfifo_size_order, GFP_KERNEL)) { > > > > This make sure we will allocate enough kfifo buffer for holding > > DJ_MAX_NUMBER_NOTIFICATIONS dj_report entries. > > Why don't you simply change __kfifo_alloc to round the allocation up > instead of down? Hi Dmitry, Yes, it would be neat and that was my first reaction as well. I then sent out a patch, but it was NACKed by Stefani(the original kfifo author). Here is the link: https://lkml.org/lkml/2012/10/26/144 Then Stefani proposed to change the API to take log of size as input to root fix this kind of issues. And here it is. Thanks. --yliu