linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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] 2/2] nvmet-tcp: set SO_PRIORITY for accepted sockets
Date: Wed, 6 Nov 2019 08:45:45 -0800	[thread overview]
Message-ID: <7f963f1c-d15a-58cb-ca9e-4c3914038a82@grimberg.me> (raw)
In-Reply-To: <B33B37937B7F3D4CB878107E305D4916D4AFCC@ORSMSX104.amr.corp.intel.com>

Reviewed-by: Sagi Grimberg <sagi@grimberg.me>

We could do this with configfs, but it given that this
is very much specific to tcp transport I find it hard to
justify.

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2019-11-06 16:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 22:27 Wunderlich, Mark
2019-11-06 16:45 ` Sagi Grimberg [this message]
2019-11-07 16:39   ` Wunderlich, Mark
2020-01-16  0:46 [PATCH " 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=7f963f1c-d15a-58cb-ca9e-4c3914038a82@grimberg.me \
    --to=sagi@grimberg.me \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mark.wunderlich@intel.com \
    --subject='Re: [PATCH] 2/2] nvmet-tcp: set SO_PRIORITY for accepted sockets' \
    /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

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).