From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Mikulas Patocka <mpatocka-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org,
Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
Laura Abbott <labbott-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
"Kirill A . Shutemov"
<kirill.shutemov-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: Re: [dm-devel] [PATCH] vmalloc: introduce vmap_pfn for persistent memory
Date: Wed, 8 Nov 2017 09:47:47 -0800 [thread overview]
Message-ID: <20171108174747.GA12199@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1711081236570.1168-Hpncn10jQN4oNljnaZt3ZvA+iT7yCHsGwRM8/txMwJMAicBL8TP8PQ@public.gmane.org>
Can you start by explaining what you actually need the vmap for?
Going through a vmap for every I/O is certainly not going to be nice
on NVDIMM-N or similar modules :)
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: linux-nvdimm@lists.01.org, Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, dm-devel@redhat.com,
Laura Abbott <labbott@redhat.com>, Christoph Hellwig <hch@lst.de>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [dm-devel] [PATCH] vmalloc: introduce vmap_pfn for persistent memory
Date: Wed, 8 Nov 2017 09:47:47 -0800 [thread overview]
Message-ID: <20171108174747.GA12199@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1711081236570.1168@file01.intranet.prod.int.rdu2.redhat.com>
Can you start by explaining what you actually need the vmap for?
Going through a vmap for every I/O is certainly not going to be nice
on NVDIMM-N or similar modules :)
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-nvdimm@lists.01.org, Christoph Hellwig <hch@lst.de>,
linux-mm@kvack.org, dm-devel@redhat.com,
Ross Zwisler <ross.zwisler@linux.intel.com>,
Laura Abbott <labbott@redhat.com>,
Dan Williams <dan.j.williams@intel.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [dm-devel] [PATCH] vmalloc: introduce vmap_pfn for persistent memory
Date: Wed, 8 Nov 2017 09:47:47 -0800 [thread overview]
Message-ID: <20171108174747.GA12199@infradead.org> (raw)
In-Reply-To: <alpine.LRH.2.02.1711081236570.1168@file01.intranet.prod.int.rdu2.redhat.com>
Can you start by explaining what you actually need the vmap for?
Going through a vmap for every I/O is certainly not going to be nice
on NVDIMM-N or similar modules :)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-08 17:47 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 22:03 [PATCH] vmalloc: introduce vmap_pfn for persistent memory Mikulas Patocka
2017-11-07 22:03 ` Mikulas Patocka
2017-11-08 9:59 ` Christoph Hellwig
2017-11-08 9:59 ` Christoph Hellwig
2017-11-08 12:33 ` Mikulas Patocka
2017-11-08 12:33 ` Mikulas Patocka
[not found] ` <alpine.LRH.2.02.1711080725490.12294-Hpncn10jQN4oNljnaZt3ZvA+iT7yCHsGwRM8/txMwJMAicBL8TP8PQ@public.gmane.org>
2017-11-08 15:04 ` Christoph Hellwig
2017-11-08 15:04 ` Christoph Hellwig
[not found] ` <20171108150447.GA10374-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-11-08 15:21 ` Mikulas Patocka
2017-11-08 15:21 ` Mikulas Patocka
2017-11-08 15:21 ` Mikulas Patocka
[not found] ` <alpine.LRH.2.02.1711081007570.8618-Hpncn10jQN4oNljnaZt3ZvA+iT7yCHsGwRM8/txMwJMAicBL8TP8PQ@public.gmane.org>
2017-11-08 15:35 ` [dm-devel] " Christoph Hellwig
2017-11-08 15:35 ` Christoph Hellwig
2017-11-08 15:35 ` Christoph Hellwig
2017-11-08 15:41 ` Dan Williams
2017-11-08 15:41 ` Dan Williams
2017-11-08 20:15 ` Mikulas Patocka
[not found] ` <alpine.LRH.2.02.1711081514320.29922-Hpncn10jQN4oNljnaZt3ZvA+iT7yCHsGwRM8/txMwJMAicBL8TP8PQ@public.gmane.org>
2017-11-08 20:25 ` Dan Williams
2017-11-08 20:25 ` Dan Williams
2017-11-08 20:25 ` Dan Williams
2017-11-09 16:40 ` Mikulas Patocka
2017-11-09 16:40 ` Mikulas Patocka
2017-11-09 16:45 ` Dan Williams
[not found] ` <CAPcyv4h48ciK7TBHm_pZ=ayUcGtDXhH-9wMV3ZAVooNs+bb0BQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-09 17:30 ` Mikulas Patocka
2017-11-09 17:30 ` Mikulas Patocka
2017-11-09 17:30 ` Mikulas Patocka
2017-11-09 17:35 ` Dan Williams
2017-11-09 17:35 ` Dan Williams
2017-11-08 17:42 ` Mikulas Patocka
[not found] ` <alpine.LRH.2.02.1711081236570.1168-Hpncn10jQN4oNljnaZt3ZvA+iT7yCHsGwRM8/txMwJMAicBL8TP8PQ@public.gmane.org>
2017-11-08 17:47 ` Christoph Hellwig [this message]
2017-11-08 17:47 ` Christoph Hellwig
2017-11-08 17:47 ` Christoph Hellwig
[not found] ` <20171108174747.GA12199-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-11-08 20:26 ` Mikulas Patocka
2017-11-08 20:26 ` Mikulas Patocka
2017-11-08 20:26 ` Mikulas Patocka
2017-11-08 21:26 ` Dan Williams
[not found] ` <CAPcyv4hR7DQ98ZCqqeyD2ihO0jWpQqPv_+s4v6iVaiNWrv96vw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-09 16:37 ` Mikulas Patocka
2017-11-09 16:37 ` Mikulas Patocka
2017-11-09 16:37 ` Mikulas Patocka
2017-11-09 16:49 ` Dan Williams
2017-11-09 16:49 ` Dan Williams
2017-11-09 18:13 ` Mikulas Patocka
2017-11-09 18:13 ` Mikulas Patocka
2017-11-09 18:38 ` Dan Williams
2017-11-09 18:38 ` Dan Williams
[not found] ` <CAPcyv4jsUuROY9Bk8xXupuJq22xRUDoiiTSqegv-njUR6MxeYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-09 18:51 ` Mikulas Patocka
2017-11-09 18:51 ` Mikulas Patocka
2017-11-09 18:51 ` Mikulas Patocka
2017-11-09 18:58 ` Dan Williams
2017-11-09 18:58 ` Dan Williams
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=20171108174747.GA12199@infradead.org \
--to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
--cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=kirill.shutemov-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=labbott-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-nvdimm-hn68Rpc1hR1g9hUCZPvPmw@public.gmane.org \
--cc=mpatocka-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.