Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Kani, Toshimitsu" <toshi.kani-ZPxbGqLxI0U@public.gmane.org>
To: "snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "linux-nvdimm-y27Ovi1pjclAfugRpC6u6w@public.gmane.org"
	<linux-nvdimm-y27Ovi1pjclAfugRpC6u6w@public.gmane.org>,
	"linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	"dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	"agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
	<agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: dm stripe: add DAX support
Date: Fri, 24 Jun 2016 18:42:20 +0000	[thread overview]
Message-ID: <1466793738.3504.404.camel@hpe.com> (raw)
In-Reply-To: <20160624182859.GD13898-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Fri, 2016-06-24 at 14:29 -0400, Mike Snitzer wrote:
> On Fri, Jun 24 2016 at  2:23pm -0400,
> Toshi Kani <toshi.kani@hpe.com> wrote:
 :
> Thanks, once jens queues the block changes I'll be able to pull this in
> to linux-dm.git
> 
> BTW, if in your testing you could evaluate/quantify any extra overhead
> from DM that'd be useful to share.  It could be there are bottlenecks
> that need to be fixed, etc.

I ran some performance tests as sanity checks (results are in ballpark), but
have not verified them carefully.  Yes, I will check to see if there are any
bottlenecks.

Thanks!
-Toshi  
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  parent reply	other threads:[~2016-06-24 18:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 18:23 [PATCH] dm stripe: add DAX support Toshi Kani
2016-06-24 18:29 ` Mike Snitzer
     [not found]   ` <20160624182859.GD13898-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-24 18:42     ` Kani, Toshimitsu [this message]
2016-07-12 22:22     ` Kani, Toshimitsu
     [not found]       ` <1468362104.8908.43.camel-ZPxbGqLxI0U@public.gmane.org>
2016-07-13  2:01         ` Mike Snitzer
     [not found]           ` <20160713020100.GA5872-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-13 15:03             ` Kani, Toshimitsu
     [not found]               ` <1468422189.8908.53.camel-ZPxbGqLxI0U@public.gmane.org>
2016-07-21  0:01                 ` Mike Snitzer
     [not found]                   ` <20160721000142.GA21913-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-07-21  3:03                     ` Jens Axboe
2016-06-24 19:58 ` [PATCH] " kbuild test robot
     [not found]   ` <201606250312.OzHHesq4%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-06-24 20:02     ` Mike Snitzer
     [not found]       ` <20160624200239.GA15587-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-06-24 20:46         ` Kani, Toshimitsu
2016-06-24 19:59 ` [PATCH] " kbuild test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1466793738.3504.404.camel@hpe.com \
    --to=toshi.kani-zpxbgqlxi0u@public.gmane.org \
    --cc=agk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nvdimm-y27Ovi1pjclAfugRpC6u6w@public.gmane.org \
    --cc=linux-raid-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox