All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: john.fastabend@gmail.com
Cc: pablo@netfilter.org, netdev@vger.kernel.org, jiri@resnulli.us,
	horms@verge.net.au
Subject: Re: [PATCH RFC 3/3] net: convert tc_u32 to use the intermediate representation
Date: Fri, 26 Feb 2016 12:34:52 -0500 (EST)	[thread overview]
Message-ID: <20160226.123452.1302145219271715730.davem@davemloft.net> (raw)
In-Reply-To: <56D066D7.2090708@gmail.com>

From: John Fastabend <john.fastabend@gmail.com>
Date: Fri, 26 Feb 2016 06:53:11 -0800

> sure but its easier for me to just consume u32 at the moment. And I
> am concerned about performance overhead with this IR. I'm going to need
> to have a performant solution eventually and I don't like converting
> into one IR only to go into another.

+1

  parent reply	other threads:[~2016-02-26 17:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 17:37 [PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion Pablo Neira Ayuso
2016-02-25 17:37 ` [PATCH RFC 1/3] net: ixgbe: add struct igxbe_filter Pablo Neira Ayuso
2016-02-25 17:37 ` [PATCH RFC 2/3] net: intermediate representation for jit translation Pablo Neira Ayuso
2016-02-25 17:37 ` [PATCH RFC 3/3] net: convert tc_u32 to use the intermediate representation Pablo Neira Ayuso
2016-02-25 20:37   ` John Fastabend
2016-02-26 14:24     ` Pablo Neira Ayuso
2016-02-26 14:53       ` John Fastabend
2016-02-26 16:02         ` Pablo Neira Ayuso
2016-02-26 16:34           ` John Fastabend
2016-02-26 17:38           ` David Miller
2016-02-26 17:34         ` David Miller [this message]
2016-02-25 18:11 ` [PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion John Fastabend
2016-02-26 11:47   ` Pablo Neira Ayuso
2016-02-26 15:42     ` John Fastabend
2016-02-26 16:19       ` Pablo Neira Ayuso
2016-02-26 16:46         ` John Fastabend
2016-02-26 17:40         ` David Miller
2016-02-26 18:53         ` Alexei Starovoitov
2016-02-26 17:26     ` David Miller

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=20160226.123452.1302145219271715730.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=horms@verge.net.au \
    --cc=jiri@resnulli.us \
    --cc=john.fastabend@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pablo@netfilter.org \
    /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.