From: Sagi Grimberg <sagi@grimberg.me>
To: "Wunderlich, Mark" <mark.wunderlich@intel.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 0/2] allow for busy poll improvements
Date: Wed, 6 Nov 2019 08:44:37 -0800 [thread overview]
Message-ID: <5f3d0fb2-7a9b-4655-1052-60ba66499746@grimberg.me> (raw)
In-Reply-To: <B33B37937B7F3D4CB878107E305D4916D4AFB9@ORSMSX104.amr.corp.intel.com>
> Proposing a small series of two patches that provide for improved packet processing for a fabric network interface that is operating with poll mode enabled
Mark,
Can we start with a series for the SO_PRIORITY for the host and the
target first? IIRC you mentioned that enabling this alone will
produce an improvement and the change is completely harmless.
Then we can add the polling change in an incremental series on that.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2019-11-06 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 22:27 [PATCH 0/2] allow for busy poll improvements Wunderlich, Mark
2019-11-06 16:44 ` Sagi Grimberg [this message]
2019-11-07 16:09 ` Wunderlich, Mark
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=5f3d0fb2-7a9b-4655-1052-60ba66499746@grimberg.me \
--to=sagi@grimberg.me \
--cc=linux-nvme@lists.infradead.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).