> Instead I gave a second thought to the solution of using dm-thin's
> public functions to access it's metadata, namely dm_thin_find_block.
> The problem is that if the mapping is not in memory I'll have to read
> it from disk, outside the critical path, and this adds complexity.
> However, since
On Thu, 4 Oct 2018 at 13:56, Joe Thornber wrote:
>
> On Wed, Oct 03, 2018 at 04:47:41PM +0100, Thanos Makatos wrote:
> > poo metadata object can return this information? I've started looking
> > at thin_bio_map(), is this the best place to start?
>
> See thin-metadata.h
>
> - Joe
I started
On Wed, Oct 03, 2018 at 04:47:41PM +0100, Thanos Makatos wrote:
> poo metadata object can return this information? I've started looking
> at thin_bio_map(), is this the best place to start?
See thin-metadata.h
- Joe
--
dm-devel mailing list
dm-devel@redhat.com
I have a kernel module that sits on top of a thin device mapper target that
receives block I/O requests and re-submits then to the thin target. I would
like to implement the following functionality: whenever I receive a write
completion from the thin target (assuming that it's the first time a
On Wed, Oct 3, 2018 at 3:47 PM Joe Thornber wrote:
>
> On Wed, Oct 03, 2018 at 03:13:36PM +0100, Thanos Makatos wrote:
> > > Could you say more about why you want to do this?
> > >
> >
> > So that I can directly read the data block without having to pass through
> > dm-thin, e.g. there might be a
On Wed, Oct 03, 2018 at 03:13:36PM +0100, Thanos Makatos wrote:
> > Could you say more about why you want to do this?
> >
>
> So that I can directly read the data block without having to pass through
> dm-thin, e.g. there might be a more direct datapath to the physical block
> device.
>
>
> Could you say more about why you want to do this?
>
So that I can directly read the data block without having to pass through
dm-thin, e.g. there might be a more direct datapath to the physical block
device.
Mappings don't change if you're not using snapshots. If you are, then any
> write
>
On Wed, Oct 03, 2018 at 01:40:22PM +0100, Thanos Makatos wrote:
> I have a kernel module that sits on top of a thin device mapper target that
> receives block I/O requests and re-submits then to the thin target. I would
> like to implement the following functionality: whenever I receive a write
>
