[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <063D6719AE5E284EB5DD2968C1650D6DB00FF62C@AcuExch.aculab.com>
Date: Fri, 16 Sep 2016 09:51:56 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Marcelo Ricardo Leitner' <marcelo.leitner@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: "linux-sctp@...r.kernel.org" <linux-sctp@...r.kernel.org>,
Neil Horman <nhorman@...driver.com>,
Vlad Yasevich <vyasevich@...il.com>
Subject: RE: [PATCH next] sctp: make use of WORD_TRUNC macro
From: Marcelo Ricardo Leitner
> Sent: 15 September 2016 19:13
> No functional change. Just to avoid the usage of '&~3'.
...
> - max_data = (asoc->pathmtu -
> - sctp_sk(asoc->base.sk)->pf->af->net_header_len -
> - sizeof(struct sctphdr) - sizeof(struct sctp_data_chunk)) & ~3;
> + max_data = asoc->pathmtu -
> + sctp_sk(asoc->base.sk)->pf->af->net_header_len -
> + sizeof(struct sctphdr) - sizeof(struct sctp_data_chunk);
> + max_data = WORD_TRUNC(max_data);
Hmmm....
Am I the only person who understands immediately what & ~3 does
but would have to grovel through the headers to find exactly what
WORD_TRUNC() does.
How big is a 'WORD' anyway??
David
Powered by blists - more mailing lists