From: roopa <roopa@cumulusnetworks•com>
To: Andy Gospodarek <gospo@cumulusnetworks•com>
Cc: sfeldma@gmail•com, netdev@vger•kernel.org,
stephen@networkplumber•org, jiri@resnulli•us, tarbal@gmail•com,
linville@tuxdriver•com
Subject: Re: [PATCH iproute2 v2] route: label externally offloaded routes
Date: Mon, 16 Mar 2015 06:46:29 -0700 [thread overview]
Message-ID: <5506DEB5.2030107@cumulusnetworks.com> (raw)
In-Reply-To: <20150316131805.GF12614@gospo.home.greyhouse.net>
On 3/16/15, 6:18 AM, Andy Gospodarek wrote:
> On Sun, Mar 15, 2015 at 12:31:34PM -0700, sfeldma@gmail•com wrote:
>> From: Scott Feldman <sfeldma@gmail•com>
>>
>> v2:
>>
>> No clear outcome on polling for choices of "external", "offload", "hw", or
>> "hardware". Andy's concern about "external" being confusing for users is
>> valid. So, I'm making executive decision to use "external_offload" for label,
>> as suggested by Jiri.
> This seems like quite a mouthful. Just make it 'offload' or 'hardware'
> so the output of 'ip route show' isn't so long that it will frequently
> be longer than 80 chars. Being longer than 80 chars is going to be
> irritating for _many_ users.
>
>
+1
next prev parent reply other threads:[~2015-03-16 13:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-15 19:31 [PATCH iproute2 v2] route: label externally offloaded routes sfeldma
2015-03-16 13:18 ` Andy Gospodarek
2015-03-16 13:46 ` roopa [this message]
2015-03-17 4:14 ` Scott Feldman
2015-03-17 7:01 ` Jiri Pirko
2015-03-17 13:24 ` Andy Gospodarek
2015-03-17 13:49 ` Jiri Pirko
2015-03-17 19:15 ` Andy Gospodarek
2015-03-24 22:51 ` Stephen Hemminger
2015-03-25 0:33 ` Andy Gospodarek
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=5506DEB5.2030107@cumulusnetworks.com \
--to=roopa@cumulusnetworks$(echo .)com \
--cc=gospo@cumulusnetworks$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=linville@tuxdriver$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfeldma@gmail$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
--cc=tarbal@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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