From: Jakub Kicinski <kuba@kernel.org>
To: Karsten Graul <kgraul@linux.ibm.com>
Cc: Tony Lu <tonylu@linux.alibaba.com>,
"D. Wythe" <alibuda@linux.alibaba.com>,
dust.li@linux.alibaba.com, 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, 13 Jan 2022 10:50:42 -0800 [thread overview]
Message-ID: <20220113105042.7a45aeb1@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> (raw)
In-Reply-To: <5a5ba1b6-93d7-5c1e-aab2-23a52727fbd1@linux.ibm.com>
On Thu, 13 Jan 2022 09:07:51 +0100 Karsten Graul wrote:
> Lets decide that when you have a specific control that you want to implement.
> I want to have a very good to introduce another interface into the SMC module,
> making the code more complex and all of that. The decision for the netlink interface
> was also done because we have the impression that this is the NEW way to go, and
> since we had no interface before we started with the most modern way to implement it.
>
> TCP et al have a history with sysfs, so thats why it is still there.
> But I might be wrong on that...
To the best of my knowledge you are correct.
next prev parent reply other threads:[~2022-01-13 18:50 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 [this message]
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
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=20220113105042.7a45aeb1@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net \
--to=kuba@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=kgraul@linux.ibm.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tonylu@linux.alibaba.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).