All of lore.kernel.org
 help / color / mirror / Atom feed
From: mark.wunderlich@intel.com (Wunderlich, Mark)
Subject: nvme-tcp: 'page must not be a Slab one'
Date: Tue, 23 Jul 2019 00:06:44 +0000	[thread overview]
Message-ID: <B33B37937B7F3D4CB878107E305D4916D15096@ORSMSX104.amr.corp.intel.com> (raw)
In-Reply-To: <6a2eedf1-8629-c5b5-257b-94cf7b3c7ae6@grimberg.me>

Thanks Sagi,

Indeed no, I did not have that patch yet.  I now see it tagged @ v5.3-rc1.
I'll move to that branch, or also try for now stable-v5.2.1 without CONFIG_DEBUG_VM.

Cheers

-----Original Message-----
From: Sagi Grimberg [mailto:sagi@grimberg.me] 
Sent: Monday, July 22, 2019 3:38 PM
To: Wunderlich, Mark <mark.wunderlich at intel.com>; linux-nvme at lists.infradead.org
Subject: Re: nvme-tcp: 'page must not be a Slab one'


> New to this list, not to NVMe_oF.? Apologize up front if this is not an appropriate use of this forum, please slap wrist appropriately if so.

This is exactly the correct forum.

> Am developing for NVMe_oF/TCP, and seeing the failure message in subject line during kernel_sendpage.
> This failure new to me starting with v5.1.? See it in v5.2 and stable 5.2.1
> 
> Wondering if this is related to 'nvme-tcp: replace sendpage calls with sendmsg calls for SLAB chunks'?.? If so, is there patch in the works to address it, or did I miss it.

Yes, this is specific to CONFIG_DEBUG_VM.

do you have this patch applied?
37c15219599f ("nvme-tcp: don't use sendpage for SLAB pages")

      reply	other threads:[~2019-07-23  0:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22 21:27 nvme-tcp: 'page must not be a Slab one' Wunderlich, Mark
2019-07-22 22:38 ` Sagi Grimberg
2019-07-23  0:06   ` Wunderlich, Mark [this message]

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=B33B37937B7F3D4CB878107E305D4916D15096@ORSMSX104.amr.corp.intel.com \
    --to=mark.wunderlich@intel.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 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.