[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200319102819.GA26418@infradead.org>
Date: Thu, 19 Mar 2020 03:28:19 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Kirill Tkhai <ktkhai@...tuozzo.com>
Cc: axboe@...nel.dk, martin.petersen@...cle.com, bob.liu@...cle.com,
darrick.wong@...cle.com, agk@...hat.com, snitzer@...hat.com,
dm-devel@...hat.com, song@...nel.org, tytso@....edu,
adilger.kernel@...ger.ca, Chaitanya.Kulkarni@....com,
ming.lei@...hat.com, osandov@...com, jthumshirn@...e.de,
minwoo.im.dev@...il.com, damien.lemoal@....com,
andrea.parri@...rulasolutions.com, hare@...e.com, tj@...nel.org,
ajay.joshi@....com, sagi@...mberg.me, dsterba@...e.com,
bvanassche@....org, dhowells@...hat.com, asml.silence@...il.com,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7 0/6] block: Introduce REQ_ALLOCATE flag for
REQ_OP_WRITE_ZEROES
On Fri, Mar 13, 2020 at 04:08:58PM +0300, Kirill Tkhai wrote:
> I just don't understand the reason nothing happens :(
> I see newly-sent patches comes fast into block tree.
> But there is only silence... I grepped over Documentation,
> and there is no special rules about block tree. So,
> it looks like standard rules should be applyable.
>
> Some comments? Some requests for reworking? Some personal reasons to ignore my patches?
I'm still completely opposed to the magic overloading using a flag.
That is just a bad design waiting for trouble to happen.
Powered by blists - more mailing lists