From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: multipart/mixed; boundary="===============7496311366003759375=="
MIME-Version: 1.0
From: Or Gerlitz <gerlitz.or at gmail.com>
Subject: [SPDK] Re: SPDK socket abstraction layer
Date: Sun, 03 Nov 2019 17:59:32 +0200
Message-ID: <CAJ3xEMg45q_=LxXoQEbODTq9+AYWjwW8mkKtv8dzLMXukB-Qew@mail.gmail.com>
In-Reply-To: 7c17efd207274a60451415e26dee896d2a7af22b.camel@intel.com
List-ID: <spdk@lists.01.org>
To: spdk@lists.01.org

--===============7496311366003759375==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 31, 2019 at 8:54 PM Walker, Benjamin
<benjamin.walker(a)intel.com> wrote:

> Here's the patch at the top of the series:
> https://review.gerrithub.io/c/spdk/spdk/+/471752

> Zero copy is getting enabled on the socket and I do see completion
> notifications, but it's always doing a deferred copy. If there was some
> description somewhere of what causes the kernel to end up doing a deferre=
d copy
> instead of page pinning that would be really useful.

the patch you pointed out doesn't change lib/nvmf/tcp.c only the sock code..
can you also refer to the patch that change nvmf
--===============7496311366003759375==--