From: David Miller <davem@davemloft.net>
To: dingtianhong@huawei.com
Cc: j.vosburgh@gmail.com, vfalico@gmail.com, andy@greyhouse.net,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] bonding: alloc the structure ad_info dynamically in per slave
Date: Wed, 14 May 2014 14:09:29 -0400 (EDT) [thread overview]
Message-ID: <20140514.140929.1272438231645943490.davem@davemloft.net> (raw)
In-Reply-To: <5370737B.5060700@huawei.com>
From: Ding Tianhong <dingtianhong@huawei.com>
Date: Mon, 12 May 2014 15:08:43 +0800
> The struct ad_slave_info is very huge, and only be used for 802.3ad mode,
> so alloc the structure dynamically could save 356 Bits for every slave in
> non 802.3ad mode.
>
> Cc: Jay Vosburgh <j.vosburgh@gmail.com>
> Cc: Veaceslav Falico <vfalico@gmail.com>
> Cc: Andy Gospodarek <andy@greyhouse.net>
> Signed-off-by: Ding Tianhong <dingtianhong@huawei.com>
Applied, thank you.
prev parent reply other threads:[~2014-05-14 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 7:08 [PATCH net-next] bonding: alloc the structure ad_info dynamically in per slave Ding Tianhong
2014-05-12 19:56 ` Veaceslav Falico
2014-05-14 18:09 ` David Miller [this message]
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=20140514.140929.1272438231645943490.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andy@greyhouse.net \
--cc=dingtianhong@huawei.com \
--cc=j.vosburgh@gmail.com \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).