From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH v2 2/2] nvme-tcp: don't use sendpage for SLAB pages
Date: Tue, 9 Jul 2019 09:37:33 -0700 [thread overview]
Message-ID: <2b2b9f09-5a02-68c8-722d-5e361ce292ed@grimberg.me> (raw)
In-Reply-To: <3206ec8102d4dae933f4638652e84349dcc50ee4.1562586804.git.mskorzhinskiy@solarflare.com>
Reviewed-by: Sagi Grimberg <sagi at grimberg.me>
next prev parent reply other threads:[~2019-07-09 16:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 11:53 [PATCH v2 0/2] Miscellaneous changes for nvme-tcp v2 Mikhail Skorzhinskii
2019-07-04 7:59 ` [PATCH v2 1/2] nvme-tcp: set the STABLE_WRITES flag when data digests are enabled Mikhail Skorzhinskii
2019-07-09 16:35 ` Sagi Grimberg
2019-07-09 21:20 ` Christoph Hellwig
2019-07-08 10:31 ` [PATCH v2 2/2] nvme-tcp: don't use sendpage for SLAB pages Mikhail Skorzhinskii
2019-07-09 16:37 ` Sagi Grimberg [this message]
2019-07-09 21:21 ` Christoph Hellwig
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=2b2b9f09-5a02-68c8-722d-5e361ce292ed@grimberg.me \
--to=sagi@grimberg.me \
/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.