public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagig@dev.mellanox.co.il>
To: Haggai Eran <haggaie@mellanox.com>,
	Roland Dreier <roland@kernel.org>,
	Latchesar Ionkov <lionkov@lanl.gov>
Cc: Or Gerlitz <gerlitz.or@gmail.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Sagi Grimberg <sagig@mellanox.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 for-next 00/16] On demand paging
Date: Wed, 10 Sep 2014 12:28:08 +0300	[thread overview]
Message-ID: <541019A8.3070005@dev.mellanox.co.il> (raw)
In-Reply-To: <54101123.2080208@mellanox.com>

On 9/10/2014 11:51 AM, Haggai Eran wrote:
<SNIP>
>
> The main benefits of ODP is the simplified programming model, simplified
> management, and avoiding worst-case memory commitment.
> For example, we were able to run multiple concurrent instances of iSER
> targets, allowing over-commitment that otherwise wouldn’t be possible.

Just wanted to add that we're talking about TGT which is a user-space 
target, thus it's RDMA memory regions were allowed to be pageable (i.e. 
not pinned).

Cheers,
Sagi.

  reply	other threads:[~2014-09-10  9:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1404377069-20585-1-git-send-email-haggaie@mellanox.com>
     [not found] ` <5405D2D8.1040700@mellanox.com>
2014-09-03 20:21   ` [PATCH v1 for-next 00/16] On demand paging Or Gerlitz
     [not found]     ` <CAOha14xthZHSpS_T+XRgZcPqwaZvtMw0iGTzKjTyjdBuLhJ4Eg@mail.gmail.com>
2014-09-03 21:15       ` Roland Dreier
2014-09-04 17:45         ` Jerome Glisse
2014-09-09 14:21         ` Haggai Eran
2014-09-10  8:51           ` Haggai Eran
2014-09-10  9:28             ` Sagi Grimberg [this message]
2014-09-12 21:16           ` Or Gerlitz
2014-09-17 15:18             ` Or Gerlitz

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=541019A8.3070005@dev.mellanox.co.il \
    --to=sagig@dev.mellanox.co.il \
    --cc=gerlitz.or@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=haggaie@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=lionkov@lanl.gov \
    --cc=roland@kernel.org \
    --cc=sagig@mellanox.com \
    /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