Thread (15 messages) 15 messages, 5 authors, 2018-06-12
STALE2948d
Revisions (5)
  1. v1 [diff vs current]
  2. v1 [diff vs current]
  3. v1 [diff vs current]
  4. v1 current
  5. v1 [diff vs current]

[PATCH 3/3] nvme: bio remapping tracepoint

From: hare@suse.de (Hannes Reinecke)
Date: 2018-06-07 11:33:32

On Thu, 7 Jun 2018 13:27:59 +0200
Christoph Hellwig [off-list ref] wrote:
On Thu, Jun 07, 2018@10:38:47AM +0200, Hannes Reinecke wrote:
quoted
Adding a tracepoint to trace bio remapping for native nvme
multipath.  
I guess we should just move the trace point into direct_make_request?

Otherwise this looks sane to me.
That would run afoul with device-mapper usage:

	case DM_MAPIO_REMAPPED:
		/* the bio has been remapped so dispatch it */
		trace_block_bio_remap(clone->bi_disk->queue, clone,
				      bio_dev(io->orig_bio), sector);
		if (md->type == DM_TYPE_NVME_BIO_BASED)
			ret = direct_make_request(clone);
		else
			ret = generic_make_request(clone);
		break;

and we can't move the call into generic_make_request().
So I fear it need to stay there.

Cheers,

Hannes
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help