From: Alex Elder <elder@linaro.org>
To: David Laight <David.Laight@ACULAB.COM>,
"subashab@codeaurora.org" <subashab@codeaurora.org>,
"stranche@codeaurora.org" <stranche@codeaurora.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"kuba@kernel.org" <kuba@kernel.org>
Cc: "sharathv@codeaurora.org" <sharathv@codeaurora.org>,
"bjorn.andersson@linaro.org" <bjorn.andersson@linaro.org>,
"evgreen@chromium.org" <evgreen@chromium.org>,
"cpratapa@codeaurora.org" <cpratapa@codeaurora.org>,
"elder@kernel.org" <elder@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2 5/6] net: qualcomm: rmnet: don't use C bit-fields in rmnet checksum trailer
Date: Mon, 8 Mar 2021 07:39:29 -0600 [thread overview]
Message-ID: <956ca2dd-d15e-ce40-e3b4-56b0f5bf2154@linaro.org> (raw)
In-Reply-To: <ebe1bf51902e49458cfdd685790c4350@AcuMS.aculab.com>
On 3/8/21 4:13 AM, David Laight wrote:
> From: Alex Elder
>> Sent: 06 March 2021 03:16
>>
>> Replace the use of C bit-fields in the rmnet_map_dl_csum_trailer
>> structure with a single one-byte field, using constant field masks
>> to encode or get at embedded values.
>>
>> Signed-off-by: Alex Elder <elder@linaro.org>
>> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
>> ---
>> .../ethernet/qualcomm/rmnet/rmnet_map_data.c | 2 +-
>> include/linux/if_rmnet.h | 17 +++++++----------
>> 2 files changed, 8 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/qualcomm/rmnet/rmnet_map_data.c
>> b/drivers/net/ethernet/qualcomm/rmnet/rmnet_map_data.c
>> index 3291f252d81b0..29d485b868a65 100644
>> --- a/drivers/net/ethernet/qualcomm/rmnet/rmnet_map_data.c
>> +++ b/drivers/net/ethernet/qualcomm/rmnet/rmnet_map_data.c
>> @@ -365,7 +365,7 @@ int rmnet_map_checksum_downlink_packet(struct sk_buff *skb, u16 len)
>>
>> csum_trailer = (struct rmnet_map_dl_csum_trailer *)(skb->data + len);
>>
>> - if (!csum_trailer->valid) {
>> + if (!u8_get_bits(csum_trailer->flags, MAP_CSUM_DL_VALID_FMASK)) {
>
> Is that just an overcomplicated way of saying:
> if (!(csum_trailer->flags & MAP_CSUM_DL_VALID_FMASK)) {
Yes it is. I defined and used all the field masks in a
consistent way, but I do think it will read better the
way you suggest. Bjorn also asked me privately whether
GENMASK(15, 15) was just the same as BIT(15) (it is).
I will post version 3 of the series, identifying which
fields are single bit/Boolean. For those I will define
the value using BIT() and will set/extract using simple
AND/OR operators. I won't use the _FMASK suffix on such
fields.
Thanks a lot for your comment/question/suggestion. I
like it.
-Alex
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>
next prev parent reply other threads:[~2021-03-08 13:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 3:15 [PATCH net-next v2 0/6] net: qualcomm: rmnet: stop using C bit-fields Alex Elder
2021-03-06 3:15 ` [PATCH net-next v2 1/6] net: qualcomm: rmnet: mark trailer field endianness Alex Elder
2021-03-06 3:15 ` [PATCH net-next v2 2/6] net: qualcomm: rmnet: simplify some byte order logic Alex Elder
2021-03-06 3:15 ` [PATCH net-next v2 3/6] net: qualcomm: rmnet: kill RMNET_MAP_GET_*() accessor macros Alex Elder
2021-03-06 3:15 ` [PATCH net-next v2 4/6] net: qualcomm: rmnet: use field masks instead of C bit-fields Alex Elder
2021-03-06 3:15 ` [PATCH net-next v2 5/6] net: qualcomm: rmnet: don't use C bit-fields in rmnet checksum trailer Alex Elder
2021-03-08 10:13 ` David Laight
2021-03-08 13:39 ` Alex Elder [this message]
2021-03-08 13:53 ` David Laight
2021-03-08 14:19 ` Alex Elder
2021-03-06 3:15 ` [PATCH net-next v2 6/6] net: qualcomm: rmnet: don't use C bit-fields in rmnet checksum header Alex Elder
2021-03-08 10:18 ` David Laight
2021-03-08 13:59 ` Alex Elder
2021-03-08 14:10 ` David Laight
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=956ca2dd-d15e-ce40-e3b4-56b0f5bf2154@linaro.org \
--to=elder@linaro.org \
--cc=David.Laight@ACULAB.COM \
--cc=bjorn.andersson@linaro.org \
--cc=cpratapa@codeaurora.org \
--cc=davem@davemloft.net \
--cc=elder@kernel.org \
--cc=evgreen@chromium.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sharathv@codeaurora.org \
--cc=stranche@codeaurora.org \
--cc=subashab@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox