From: Sagi Grimberg <sagi@grimberg.me>
To: amit.engel@dell.com, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet-tcp: Add a multex lock to start_queue failure case
Date: Tue, 15 Jun 2021 11:02:10 -0700 [thread overview]
Message-ID: <c79420e6-8110-4367-8361-cf1244f60318@grimberg.me> (raw)
In-Reply-To: <20210610084112.30400-1-amit.engel@dell.com>
> From: Amit Engel <amit.engel@dell.com>
>
> this is in order to serialize nvme_tcp_stop_queue
Thinking about this, I don't think this is needed, can you describe
what is the scenario that requires this protection?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2021-06-15 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 8:41 [PATCH] nvmet-tcp: Add a multex lock to start_queue failure case amit.engel
2021-06-15 18:02 ` Sagi Grimberg [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=c79420e6-8110-4367-8361-cf1244f60318@grimberg.me \
--to=sagi@grimberg.me \
--cc=amit.engel@dell.com \
--cc=linux-nvme@lists.infradead.org \
/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.