From: Hangbin Liu <liuhangbin@gmail.com>
To: Nikolay Aleksandrov <nikolay@nvidia.com>
Cc: netdev@vger.kernel.org, Jay Vosburgh <j.vosburgh@gmail.com>,
Veaceslav Falico <vfalico@gmail.com>,
Andy Gospodarek <andy@greyhouse.net>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, David Ahern <dsahern@gmail.com>
Subject: Re: [PATCH RFC net-next 3/5] bonding: add ip6_addr for bond_opt_value
Date: Fri, 28 Jan 2022 16:04:54 +0800 [thread overview]
Message-ID: <YfOjpuyiiwp+UffI@Laptop-X1> (raw)
In-Reply-To: <e080838e-ea33-7340-716c-f61cd57c32fd@nvidia.com>
On Thu, Jan 27, 2022 at 02:14:16PM +0200, Nikolay Aleksandrov wrote:
> Yeah, something like that so you can pass around larger items in the extra storage, but please
> keep it to the minimum e.g. 16 bytes for this case as we have many static bond_opt_values
> and pass it around a lot.
OK, I will update the patch after Chinese new year holiday.
Thanks
Hangbin
next prev parent reply other threads:[~2022-01-28 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 7:35 [PATCH RFC net-next 0/5] bonding: add IPv6 NS/NA monitor support Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 1/5] ipv6: separate ndisc_ns_create() from ndisc_send_ns() Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 2/5] Bonding: split bond_handle_vlan from bond_arp_send Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 3/5] bonding: add ip6_addr for bond_opt_value Hangbin Liu
2022-01-26 11:35 ` Nikolay Aleksandrov
2022-01-27 7:02 ` Hangbin Liu
2022-01-27 8:56 ` Nikolay Aleksandrov
2022-01-27 12:09 ` Hangbin Liu
2022-01-27 12:14 ` Nikolay Aleksandrov
2022-01-28 8:04 ` Hangbin Liu [this message]
2022-01-26 7:35 ` [PATCH RFC net-next 4/5] bonding: add new parameter ns_targets Hangbin Liu
2022-01-26 7:35 ` [PATCH RFC net-next 5/5] bonding: add new option ns_ip6_target Hangbin Liu
2022-01-26 11:47 ` [PATCH RFC net-next 0/5] bonding: add IPv6 NS/NA monitor support Nikolay Aleksandrov
2022-01-27 7:13 ` Hangbin Liu
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=YfOjpuyiiwp+UffI@Laptop-X1 \
--to=liuhangbin@gmail.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=j.vosburgh@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@nvidia.com \
--cc=vfalico@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox