[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200520233913.GV2491@localhost.localdomain>
Date: Wed, 20 May 2020 20:39:13 -0300
From: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
To: David Miller <davem@...emloft.net>
Cc: hch@....de, kuba@...nel.org, edumazet@...gle.com,
kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org, vyasevich@...il.com,
nhorman@...driver.com, jmaloy@...hat.com, ying.xue@...driver.com,
drbd-dev@...ts.linbit.com, linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org, linux-nvme@...ts.infradead.org,
target-devel@...r.kernel.org, linux-afs@...ts.infradead.org,
linux-cifs@...r.kernel.org, cluster-devel@...hat.com,
ocfs2-devel@....oracle.com, netdev@...r.kernel.org,
linux-sctp@...r.kernel.org, ceph-devel@...r.kernel.org,
rds-devel@....oracle.com, linux-nfs@...r.kernel.org
Subject: Re: [PATCH 31/33] sctp: add sctp_sock_set_nodelay
On Wed, May 20, 2020 at 04:23:55PM -0700, David Miller wrote:
> From: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>
> Date: Wed, 20 May 2020 20:10:01 -0300
>
> > The duplication with sctp_setsockopt_nodelay() is quite silly/bad.
> > Also, why have the 'true' hardcoded? It's what dlm uses, yes, but the
> > API could be a bit more complete than that.
>
> The APIs are being designed based upon what in-tree users actually
> make use of. We can expand things later if necessary.
Sometimes expanding things later can be though, thus why the worry.
But ok, I get it. Thanks.
The comment still applies, though. (re the duplication)
Powered by blists - more mailing lists