From: Ernest Zaslavsky <kreuzerkrieg at gmail.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Memory buffer allocation in SPDK
Date: Wed, 07 Feb 2018 17:01:16 +0200 [thread overview]
Message-ID: <5a7b14be.06d1df0a.a6011.58c6@mx.google.com> (raw)
In-Reply-To: D545A357-5C00-4AC2-B809-AD14DAFF7729@intel.com
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Great! Thanks!
Sent from Mail for Windows 10
From: Harris, James R
Sent: Wednesday, February 7, 2018 5:00 PM
To: Storage Performance Development Kit
Subject: Re: [SPDK] Memory buffer allocation in SPDK
From: SPDK <spdk-bounces(a)lists.01.org> on behalf of Ernest Zaslavsky <kreuzerkrieg(a)gmail.com>
Reply-To: Storage Performance Development Kit <spdk(a)lists.01.org>
Date: Tuesday, February 6, 2018 at 10:51 PM
To: Storage Performance Development Kit <spdk(a)lists.01.org>
Subject: Re: [SPDK] Memory buffer allocation in SPDK
Hi James,
Thanks for the info, sounds like we have a way to solve our problem. I have some additional questions. The spdk_mem_register() function, it just adds the region to the SPDK allocation map, right? It does not touch or modifies the memory in any way, right? Is it safe to say that we may register with SPDK all our pre-allocated memory when the application starts and just keep it that way?
Hi Ernest,
Correct – SPDK does not touch the buffer registered with spdk_mem_register() in any way – it only adds it to any registered translation maps.
-Jim
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 3736 bytes --]
next reply other threads:[~2018-02-07 15:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 15:01 Ernest Zaslavsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-07 15:00 [SPDK] Memory buffer allocation in SPDK Harris, James R
2018-02-07 5:51 Ernest Zaslavsky
2018-02-07 0:11 Harris, James R
2018-02-06 13:32 Ernest Zaslavsky
2016-12-13 16:05 [SPDK] Memory Buffer Allocation " Harris, James R
2016-12-13 15:49 yzhu
2016-12-13 4:46 Harris, James R
2016-12-13 4:13 yzhu
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=5a7b14be.06d1df0a.a6011.58c6@mx.google.com \
--to=spdk@lists.01.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