Hello, Paolo. On Mon, Jun 10, 2019 at 04:49:47PM +0200, Paolo Valente wrote: > 1) General solution allowing multiple entities to share common files: > rejected by Tejun. It was printing outputs from multiple policies for the same device in the same file without any way of telling which one is actually being used. It can't work that way. We can't show stuff which don't make sense to users as a part of the kernel interface. A general solution, if we want to pursue, would be in this direction but something which actually considers what's being used where, but an easier alternative would be selecting the active policy system-wide. > 2) Simple replacement bfq.weight -> weight, after the only entity > using that name, cfq, has gone: rejected by Jens because it is a > disruptive change of the interface. > 3) Symlink, proposed by Johannes: maybe rejected by Tejun. > Tejun, could you please tell us whether you may accept the last > option? This option may be associated with deprecating the explicit > use of bfq.weight (I don't know of anybody who wants to use this > confusing name). So, in a few releases we could finally drop this > bfq.weight and turn the symlink back into an actual interface file. Yeah, it'd either have to be 2) or 3) but I wasn't really engaged in the discussion. The simplest would be just renaming the interface file given that that was ppl were using anyway. Jens, if you aren't too opposed to it, let's just rename bfq.weight to weight. Thanks. -- tejun
