From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755401AbaEFUj4 (ORCPT ); Tue, 6 May 2014 16:39:56 -0400 Received: from cdptpa-outbound-snat.email.rr.com ([107.14.166.227]:32957 "EHLO cdptpa-oedge-vip.email.rr.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754545AbaEFUjz (ORCPT ); Tue, 6 May 2014 16:39:55 -0400 Date: Tue, 6 May 2014 16:39:50 -0400 From: Steven Rostedt To: Dan Streetman Cc: Hugh Dickins , Andrew Morton , Mel Gorman , Michal Hocko , Christian Ehrhardt , Rik van Riel , Weijie Yang , Johannes Weiner , Linux-MM , linux-kernel , Paul Gortmaker , Thomas Gleixner , Peter Zijlstra Subject: Re: [PATCH 3/4] plist: add plist_rotate Message-ID: <20140506163950.7e278f7c@gandalf.local.home> In-Reply-To: References: <1397336454-13855-1-git-send-email-ddstreet@ieee.org> <1399057350-16300-1-git-send-email-ddstreet@ieee.org> <1399057350-16300-4-git-send-email-ddstreet@ieee.org> <20140505221846.4564e04d@gandalf.local.home> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-RR-Connecting-IP: 107.14.168.130:25 X-Cloudmark-Score: 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 6 May 2014 16:12:54 -0400 Dan Streetman wrote: > On Mon, May 5, 2014 at 10:18 PM, Steven Rostedt wrote: > > On Fri, 2 May 2014 15:02:29 -0400 > > Dan Streetman wrote: > > > >> Add plist_rotate(), which moves the specified plist_node after > >> all other same-priority plist_nodes in the list. > > > > This is a little confusing? You mean it takes a plist_node from a plist > > and simply moves it to the end of the list of all other nodes of the > > same priority? > > yes, exactly > > > Kind of like what a sched_yield() would do with a > > SCHED_FIFO task? I wonder if we should call this "plist_yield()" then? > > I suppose it is similar, yes...I'll rename it in a v2 patch. I'm open to other suggestions as well. What else can give you the idea that it's putting a node at the end of its priority? I added Peter to the Cc list because I know how much he loves sched_yield() :-) > > > > >> > >> This is needed by swap, which has a plist of swap_info_structs > >> and needs to use each same-priority swap_info_struct equally. > > > > "needs to use each same-priority swap_info_struct equally" > > > > -ENOCOMPUTE > > heh, yeah that needs a bit more explaining doesn't it :-) > > by "equally", I mean as swap writes pages out to its swap devices, it > must write to any same-priority devices on a round-robin basis. OK, I think you are suffering from "being too involved to explain clearly" syndrome. :) I still don't see the connection between swap pages and plist, and even more so, why something would already be in a plist and then needs to be pushed to the end of its priority. > > I'll update the comment in the v2 patch to try to explain clearer. > Please do. But explain it to someone that has no idea how plists are used by the swap subsystem, and why you need to move a node to the end of its priority. Thanks, -- Steve