From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: [PATCH RFC RESEND 00/14] New version of the BFQ I/O Scheduler Date: Fri, 30 May 2014 13:39:17 -0400 Message-ID: <20140530173917.GJ24871@htj.dyndns.org> References: <1401194558-5283-1-git-send-email-paolo.valente@unimore.it> <20140530173146.GG16605@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=ZfUjvLLNTwEfhiExDp3z/anbwzV9oGRHvhgeWrld8hc=; b=nn+oIDCeKzp0c+MpgDyndeQI0ZXdEoFMX9nT4h3BPD32od3zT8RGvqLqUXWSqhQowB g1sb9ioUmOlad+mHfpsVQRrITk5B7SXSdIXn22NLRQFHojb8sO/DVlCM/rCLQvMlXL9F Ia6ffKbWdlXHsBKKMDkh9O2Z7XnFE7yY19GGuULeT+gm6FzirHvcVKsdxVf/DRLuzsFH n1e/yknoIk3VkfHVtjxcsZmSNtsqXCKx+L3w8wJfgGi0lJPX0eW1kVeqdNTfC+ftlU8x zHIwUz8wO/C5aWLhryIIk0PDq+KEyyVkOOpIaTBqeyhP9q3+26ds2WuxG9YwdpgTz3lz zzow== Content-Disposition: inline In-Reply-To: <20140530173146.GG16605-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Vivek Goyal Cc: Jens Axboe , paolo , containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Fabio Checconi , Arianna Avanzini , cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Paolo Valente On Fri, May 30, 2014 at 01:31:46PM -0400, Vivek Goyal wrote: > > What allows BFQ to provide the above features is its accurate > > scheduling engine (patches 1-4), combined with a set of simple > > heuristics and improvements (patches 5-14). > > This is very hard to understand. This puzzle need to be broken down > into small pieces and explained in simple design terms so that even > 5 years down the line I can explain why BFQ was better. Vivek, stop wasting people's time and just go study the paper. Let's *please* talk after that. What do you expect him to do? Copy & paste the whole paper here and walk you through each step of it? He presented as much information as he could and then provided sufficient summary in the head message and as comments in the implementation. It's now *your* turn to study what has been presented. Sure, if you have further questions or think that the implementation and patches need more documentation, that's completely fine but I find it ridiculous that you're demanding to be spoon-fed information which is readily available in an easily consumable form. Seriously, this is the best documentation we've had in this area *EVER*. -- tejun