From: Martin Wilck <mwilck@suse.com>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
Christoph Hellwig <hch@lst.de>, Chao Leng <lengchao@huawei.com>,
Hannes Reinecke <hare@suse.de>, Daniel Wagner <dwagner@suse.de>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2] nvme: rdma/tcp: call nvme_mpath_stop() from reconnect workqueue
Date: Fri, 23 Apr 2021 19:09:04 +0200 [thread overview]
Message-ID: <f883e44164bdb124050ed12837a6f735cb10607c.camel@suse.com> (raw)
In-Reply-To: <b2315ed2e6e1c273c9e000b107c38e41e2ddd33c.camel@suse.com>
On Fri, 2021-04-23 at 18:43 +0200, Martin Wilck wrote:
> On Fri, 2021-04-23 at 17:50 +0200, Maurizio Lombardi wrote:
> > Hello,
> >
> > pá 23. 4. 2021 v 15:49 odesílatel <mwilck@suse.com> napsal:
> > > From: Martin Wilck <mwilck@suse.com>
> > >
> > > diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
> > > index a0f00cb8f9f3..46287b4f4d10 100644
> > > --- a/drivers/nvme/host/tcp.c
> > > +++ b/drivers/nvme/host/tcp.c
> > > @@ -2068,6 +2068,7 @@ static void
> > > nvme_tcp_error_recovery_work(struct
> > > work_struct *work)
> > > return;
> > > }
> > >
> > > + nvme_mpath_stop(ctrl);
> > > nvme_tcp_reconnect_or_remove(ctrl);
> > > }
> > >
> >
> >
> > Do you think it would make sense to call nvme_mpath_stop()
> > inside nvme_tcp_reconnect_ctrl_work() too?
> > Right before it requeues itself by calling
> > nvme_tcp_reconnect_or_remove(ctrl)?
>
> Good point, probably yes. I'll have another look.
I did now, and I don't think it's necessary. With my patch,
nvme_mpath_stop() will be called the before the first invocation of
nvme_tcp_reconnect_ctrl_work(). The anatt timer and mpath work queue
will only be started if nvme_tcp_setup_ctrl() succeeds, so we don't
need to stop them again when it fails.
Regards
Martin
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-04-23 17:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 13:38 [PATCH v2] nvme: rdma/tcp: call nvme_mpath_stop() from reconnect workqueue mwilck
[not found] ` <CAFL455k3aBLcZrZPq=Q-9aws4UesstA5gSOr_E7mEFrLT+KbKw@mail.gmail.com>
2021-04-23 16:43 ` Martin Wilck
2021-04-23 17:09 ` Martin Wilck [this message]
2021-04-24 0:21 ` Sagi Grimberg
2021-04-26 14:51 ` Christoph Hellwig
2021-04-26 16:27 ` Martin Wilck
2021-04-27 1:45 ` Chao Leng
2021-04-27 7:30 ` Martin Wilck
2021-04-27 8:56 ` Martin Wilck
2021-04-27 9:04 ` Martin Wilck
2021-04-25 1:07 ` Chao Leng
2021-04-25 11:34 ` Hannes Reinecke
2021-04-26 2:31 ` Chao Leng
2021-04-26 15:18 ` Martin Wilck
2021-04-26 9:34 ` Martin Wilck
2021-04-26 10:06 ` Hannes Reinecke
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=f883e44164bdb124050ed12837a6f735cb10607c.camel@suse.com \
--to=mwilck@suse.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=lengchao@huawei.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@redhat.com \
--cc=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.