From: Stephen Hemminger <stephen@networkplumber.org>
To: Jian Shen <shenjian15@huawei.com>
Cc: <davem@davemloft.net>, <kuba@kernel.org>,
<netdev@vger.kernel.org>, <linuxarm@openeuler.org>
Subject: Re: [RFC net-next] net: extend netdev features
Date: Sat, 10 Jul 2021 08:11:20 -0700 [thread overview]
Message-ID: <20210710081120.5570fb87@hermes.local> (raw)
In-Reply-To: <1625910047-56840-1-git-send-email-shenjian15@huawei.com>
On Sat, 10 Jul 2021 17:40:47 +0800
Jian Shen <shenjian15@huawei.com> wrote:
> For the prototype of netdev_features_t is u64, and the number
> of netdevice feature bits is 64 now. So there is no space to
> introduce new feature bit.
>
> I did a small change for this. Keep the prototype of
> netdev_feature_t, and extend the feature members in struct
> net_device to an array of netdev_features_t. So more features
> bits can be used.
>
> As this change, some functions which use netdev_features_t as
> parameter or returen value will be affected.
> I did below changes:
> a. parameter: "netdev_features_t" to "netdev_features_t *"
> b. return value: "netdev_feature_t" to "void", and add
> "netdev_feature_t *" as output parameter.
>
> I kept some functions no change, which are surely useing the
> first 64 bit of net device features now, such as function
> nedev_add_tso_features(). In order to minimize to changes.
>
> For the features are array now, so it's unable to do logical
> operation directly. I introduce a inline function set for
> them, including "netdev_features_and/andnot/or/xor/equal/empty".
>
> For NETDEV_FEATURE_COUNT may be more than 64, so the shift
> operation for NETDEV_FEATURE_COUNT is illegal. I changed some
> macroes and functions, which does shift opertion with it.
>
> I haven't finished all the changes, for it affected all the
> drivers which use the feature, need more time and test. I
> sent this RFC patch, want to know whether this change is
> acceptable, and how to improve it.
>
> Any comments will be helpful.
>
> Signed-off-by: Jian Shen <shenjian15@huawei.com>
Infrastructure changes must be done as part of the patch that
needs the new feature bit. It might be that your feature bit is
not accepted as part of the review cycle, or a better alternative
is proposed.
next prev parent reply other threads:[~2021-07-10 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 9:40 [RFC net-next] net: extend netdev features Jian Shen
2021-07-10 11:50 ` kernel test robot
2021-07-10 12:14 ` kernel test robot
2021-07-10 15:11 ` Stephen Hemminger [this message]
2021-07-10 15:16 ` Andrew Lunn
2021-07-10 15:35 ` Dave Taht
2021-07-10 20:32 ` Stephen Hemminger
2021-07-12 2:43 ` shenjian (K)
2021-07-10 15:29 ` Andrew Lunn
[not found] ` <2b6bc8a7-6fe3-b42e-070d-f9a81560ecda@huawei.com>
2021-07-13 13:53 ` Andrew Lunn
2021-07-15 6:34 ` shenjian (K)
2021-07-10 19:05 ` Heiner Kallweit
2021-07-12 3:41 ` shenjian (K)
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=20210710081120.5570fb87@hermes.local \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linuxarm@openeuler.org \
--cc=netdev@vger.kernel.org \
--cc=shenjian15@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.