Re: [PATCH RFC 0/3] block,ext4: Introduce REQ_OP_ASSIGN_RANGE to reflect extents allocation in block device internals

From: Chaitanya Kulkarni
Date: Wed Dec 11 2019 - 02:43:03 EST

Next message: Christoph Hellwig: "Re: [PATCH] iommu: fix min_not_zero() type mismatch warning"
Previous message: Greg Kroah-Hartman: "Re: [PATCH 2/2] staging: octeon-usb: delete the octeon usb host controller driver"
In reply to: Kirill Tkhai: "[PATCH RFC 1/3] block: Add support for REQ_OP_ASSIGN_RANGE operation"
Next in thread: Kirill Tkhai: "Re: [PATCH RFC 0/3] block,ext4: Introduce REQ_OP_ASSIGN_RANGE to reflect extents allocation in block device internals"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Here is a simple test I did:
> https://gist.github.com/tkhai/5b788651cdb74c1dbff3500745878856
>

Somehow I'm not able to open this link, can you please share results
in plain text on the email ?

Next message: Christoph Hellwig: "Re: [PATCH] iommu: fix min_not_zero() type mismatch warning"
Previous message: Greg Kroah-Hartman: "Re: [PATCH 2/2] staging: octeon-usb: delete the octeon usb host controller driver"
In reply to: Kirill Tkhai: "[PATCH RFC 1/3] block: Add support for REQ_OP_ASSIGN_RANGE operation"
Next in thread: Kirill Tkhai: "Re: [PATCH RFC 0/3] block,ext4: Introduce REQ_OP_ASSIGN_RANGE to reflect extents allocation in block device internals"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]