From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chad Talbott Subject: Re: [Lsf] Preliminary Agenda and Activities for LSF Date: Tue, 29 Mar 2011 13:14:13 -0700 Message-ID: References: <1301373398.2590.20.camel@mulgrave.site> <20110329190921.GH24485@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: James Bottomley , lsf@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org To: Vivek Goyal Return-path: Received: from smtp-out.google.com ([216.239.44.51]:42841 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753528Ab1C2UOT convert rfc822-to-8bit (ORCPT ); Tue, 29 Mar 2011 16:14:19 -0400 Received: from hpaq6.eem.corp.google.com (hpaq6.eem.corp.google.com [172.25.149.6]) by smtp-out.google.com with ESMTP id p2TKEGOp006839 for ; Tue, 29 Mar 2011 13:14:16 -0700 Received: from pzk35 (pzk35.prod.google.com [10.243.19.163]) by hpaq6.eem.corp.google.com with ESMTP id p2TKEDRY014423 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Tue, 29 Mar 2011 13:14:15 -0700 Received: by pzk35 with SMTP id 35so127583pzk.34 for ; Tue, 29 Mar 2011 13:14:13 -0700 (PDT) In-Reply-To: <20110329190921.GH24485@redhat.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tue, Mar 29, 2011 at 12:09 PM, Vivek Goyal wrote= : > On Tue, Mar 29, 2011 at 10:35:13AM -0700, Chad Talbott wrote: >> I'd like to propose a discussion topic: >> >> IO-less Dirty Throttling Considered Harmful... >> > > I see that writeback has extended session at 10.00. I am assuming > IO less throttling will be discussed there. Is it possible to > discuss its effect on block cgroups there? I am not sure enough > time is there because it ties in memory cgroup also. > > Or there is a session at 12.30 "memcg dirty limits and writeback", it > can probably be discussed there too. I just want to make sure that the topic is discussed and I don't want to eat into someone else's time. I'll be sure to bring it up if it's not granted a dedicated session. >> to isolation and cgroup IO schedulers in general. =A0The disk schedu= ler >> is knocked out of the picture unless it can see the IO generated by >> each group above it. =A0The world of memcg-aware writeback stacked o= n >> top of block-cgroups is a complicated one. =A0Throttling in >> balance_dirty_pages() will likely be a non-starter for current users >> of group-aware CFQ. > > Can't a single flusher thread keep all the groups busy/full on slow > SATA device. A single flusher thread *could* keep all the groups busy and full, but the current implementation does nothing explicit to make that happen. I'd like to make sure that this case is considered, independent of a particular implementation. Chad -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html