From mboxrd@z Thu Jan 1 00:00:00 1970 From: 'Marcelo Ricardo Leitner' Subject: Re: [PATCHv2 net-next 04/12] sctp: implement make_datafrag for sctp_stream_interleave Date: Fri, 8 Dec 2017 13:15:38 -0200 Message-ID: <20171208151538.GT13341@localhost.localdomain> References: <2ca21c61e82a44daa29226eac54a4950@AcuMS.aculab.com> <20171208145630.GE3328@localhost.localdomain> <67253734d93744a2b3b05d4a0bbe4a8f@AcuMS.aculab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: 'Xin Long' , network dev , "linux-sctp@vger.kernel.org" , Neil Horman , "davem@davemloft.net" To: David Laight Return-path: Received: from mail-qt0-f194.google.com ([209.85.216.194]:38625 "EHLO mail-qt0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753791AbdLHPPo (ORCPT ); Fri, 8 Dec 2017 10:15:44 -0500 Content-Disposition: inline In-Reply-To: <67253734d93744a2b3b05d4a0bbe4a8f@AcuMS.aculab.com> Sender: netdev-owner@vger.kernel.org List-ID: On Fri, Dec 08, 2017 at 03:01:31PM +0000, David Laight wrote: > From: Marcelo Ricardo Leitner > > Sent: 08 December 2017 14:57 > > > > On Fri, Dec 08, 2017 at 02:06:04PM +0000, David Laight wrote: > > > From: Xin Long > > > > Sent: 08 December 2017 13:04 > > > ... > > > > @@ -264,8 +264,8 @@ struct sctp_datamsg *sctp_datamsg_from_user(struct sctp_association *asoc, > > > > frag |= SCTP_DATA_SACK_IMM; > > > > } > > > > > > > > - chunk = sctp_make_datafrag_empty(asoc, sinfo, len, frag, > > > > - 0, GFP_KERNEL); > > > > + chunk = asoc->stream.si->make_datafrag(asoc, sinfo, len, frag, > > > > + GFP_KERNEL); > > > > > > I know that none of the sctp code is very optimised, but that indirect > > > call is going to be horrid. > > > > Yeah.. but there is no way to avoid the double derreference > > considering we only have the asoc pointer in there and we have to > > reach the contents of the data chunk operations struct, and the .si > > part is the same as 'stream' part as it's a constant offset. > ... > > It isn't only the double indirect, the indirect call itself isn't 'fun'. I meant in this context. The indirect call is so we don't have to flood the stack with if (old data chunk fmt) { ... } else { ... } So instead of this, we now have some key operations identified and wrapped up behind this struct, allowing us to abstract whatever data chunk format it is. > > I think there are other hot paths where you've replaced a sizeof() > with a ?: clause. > Caching the result might be much better. The only new ?: clause I could find this patchset is on patch 12 and has nothing to do with sizeof(). The sizeof() results are indeed cached, as you can see in patch 4: +static struct sctp_stream_interleave sctp_stream_interleave_0 = { + .data_chunk_len = sizeof(struct sctp_data_chunk), and the two helpers on it at the begining of the patch. Marcelo