netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Andy Gospodarek <gospo@cumulusnetworks.com>
Cc: Jiri Pirko <jiri@resnulli.us>, Scott Feldman <sfeldma@gmail.com>,
	Netdev <netdev@vger.kernel.org>,
	Roopa Prabhu <roopa@cumulusnetworks.com>,
	Jeff Kirsher <tarbal@gmail.com>,
	John Linville <linville@tuxdriver.com>
Subject: Re: [PATCH iproute2 v2] route: label externally offloaded routes
Date: Tue, 24 Mar 2015 15:51:37 -0700	[thread overview]
Message-ID: <20150324155137.03671191@urahara> (raw)
In-Reply-To: <20150317191557.GB18165@gospo.home.greyhouse.net>

On Tue, 17 Mar 2015 15:15:57 -0400
Andy Gospodarek <gospo@cumulusnetworks.com> wrote:

> On Tue, Mar 17, 2015 at 02:49:21PM +0100, Jiri Pirko wrote:
> > Tue, Mar 17, 2015 at 02:24:56PM CET, gospo@cumulusnetworks.com wrote:
> > >On Mon, Mar 16, 2015 at 09:14:50PM -0700, Scott Feldman wrote:
> > >> On Mon, Mar 16, 2015 at 6:18 AM, Andy Gospodarek
> > >> <gospo@cumulusnetworks.com> 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.
> > >> 
> > >> Andy, since you have passion on this topic, would you mind taking it
> > >> from here to get consensus, and post an updated patch, if needed?
> > >
> > >Absolutely.  I felt bad responding with more complaints yesterday
> > >without proposing an alternative patch.
> > >
> > >I'll be happy to handle this -- it will elimininate at least one
> > >complainer!
> > >
> > >
> > >> I was about to suggest a new made-up work like "keroff" and someday
> > >> the new word is added to Websters .  Daddy, what's "keroff"?  Oh son,
> > >> that means "offloaded from kernel to external device".  Ya, actually,
> > >> that's my vote: keroff.
> > 
> > Hmm, on the second thought, shouldn't it be rather "extoff" ?
> > 
> 
> I'm really liking the sound of 'extoffk'  ;)
> 

I am bouncing this patch, come back when you decide on a name.

  reply	other threads:[~2015-03-24 22:51 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
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 [this message]
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=20150324155137.03671191@urahara \
    --to=stephen@networkplumber.org \
    --cc=gospo@cumulusnetworks.com \
    --cc=jiri@resnulli.us \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=sfeldma@gmail.com \
    --cc=tarbal@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).