From: Willy Tarreau <w@1wt.eu>
To: Eric Dumazet <edumazet@google.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
netdev <netdev@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH stable 4.9 1/8] x86: bpf_jit: small optimization in emit_bpf_tail_call()
Date: Mon, 29 Jan 2018 15:06:16 +0100 [thread overview]
Message-ID: <20180129140616.GA23326@1wt.eu> (raw)
In-Reply-To: <CANn89iKbXNBJcteAtZpkM=u5dwcTGALNWc9rektdz1BHVuGb+g@mail.gmail.com>
Hi Eric,
On Mon, Jan 29, 2018 at 06:04:30AM -0800, Eric Dumazet wrote:
> > If these 4 bytes matter, why not use
> > cmpq with an immediate value instead, which saves 2 extra bytes ? :
> >
> > - the mov above is 11 bytes total :
> >
> > 0: 48 8b 84 d6 78 56 34 mov 0x12345678(%rsi,%rdx,8),%rax
> > 7: 12
> > 8: 48 85 c0 test %rax,%rax
> >
> > - the equivalent cmp is only 9 bytes :
> >
> > 0: 48 83 bc d6 78 56 34 cmpq $0x0,0x12345678(%rsi,%rdx,8)
> > 7: 12 00
> >
> > And as a bonus, it doesn't even clobber rax.
> >
> > Just my two cents,
>
>
> Hi Willy
>
> Please look more closely at following instructions.
>
> We need the value later, not only testing it being zero :)
Ah OK that makes total sense then ;-)
Thanks,
willy
prev parent reply other threads:[~2018-01-29 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1517190206.git.daniel@iogearbox.net>
[not found] ` <0f909080f2ef055783fc7b394e8111e0df3c4971.1517190206.git.daniel@iogearbox.net>
2018-01-29 6:39 ` [PATCH stable 4.9 1/8] x86: bpf_jit: small optimization in emit_bpf_tail_call() Willy Tarreau
2018-01-29 14:04 ` Eric Dumazet
2018-01-29 14:06 ` Willy Tarreau [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=20180129140616.GA23326@1wt.eu \
--to=w@1wt.eu \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.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 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).