From: Karsten Graul <kgraul@linux.ibm.com>
To: "D. Wythe" <alibuda@linux.alibaba.com>
Cc: dust.li@linux.alibaba.com, kuba@kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next v2] net/smc: Reduce overflow of smc clcsock listen queue
Date: Thu, 6 Jan 2022 10:54:02 +0100 [thread overview]
Message-ID: <ffe855d4-982b-25e6-a901-747095364bd0@linux.ibm.com> (raw)
In-Reply-To: <cdbb6235-34dd-bc65-304d-0f09accad6a3@linux.alibaba.com>
On 06/01/2022 04:51, D. Wythe wrote:
>
> One problem for the fallback scenario is that server must actively send decline message to client and wait for the clc proposal message that client may already sent, otherwise the message of SMC handshake may be read by user space application, which will also lead to OOM conditions caused by infinite amount of dangling sockets.
>
> In that case, we have to make restrictions on 'SMC fallback ing', which makes things more complicated.
Thats a good point, I need to think about this ....
prev parent reply other threads:[~2022-01-06 9:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 13:12 [PATCH net-next v2] net/smc: Reduce overflow of smc clcsock listen queue D. Wythe
2022-01-04 13:45 ` Karsten Graul
2022-01-04 16:17 ` D. Wythe
2022-01-05 4:40 ` D. Wythe
2022-01-05 8:28 ` Tony Lu
2022-01-05 8:57 ` dust.li
2022-01-05 13:17 ` Karsten Graul
2022-01-05 15:06 ` D. Wythe
2022-01-05 19:13 ` Karsten Graul
2022-01-06 7:05 ` Tony Lu
2022-01-13 8:07 ` Karsten Graul
2022-01-13 18:50 ` Jakub Kicinski
2022-01-20 13:39 ` Tony Lu
2022-01-20 16:00 ` Stefan Raspl
2022-01-21 2:47 ` Tony Lu
2022-02-16 11:46 ` dust.li
2022-01-06 3:51 ` D. Wythe
2022-01-06 9:54 ` Karsten Graul [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=ffe855d4-982b-25e6-a901-747095364bd0@linux.ibm.com \
--to=kgraul@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.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.