[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2e27b8d9-4615-cd8d-93de-2adb75d8effa@intel.com>
Date: Thu, 31 Oct 2019 15:38:42 -0700
From: "Samudrala, Sridhar" <sridhar.samudrala@...el.com>
To: bjorn.topel@...il.com
Cc: alexei.starovoitov@...il.com, bjorn.topel@...el.com,
bpf@...r.kernel.org, intel-wired-lan@...ts.osuosl.org,
jakub.kicinski@...ronome.com, maciej.fijalkowski@...el.com,
magnus.karlsson@...el.com, netdev@...r.kernel.org,
sridhar.samudrala@...el.com, toke@...hat.com, tom.herbert@...el.com
Subject: Re: [Intel-wired-lan] FW: [PATCH bpf-next 2/4] xsk: allow AF_XDP
sockets to receive packets directly from a queue
[...]
> >
> > With mitigations ON
> > -------------------
> > Samples: 6K of event 'cycles', 4000 Hz, Event count (approx.): 5646512726
> > bpf_prog_3c8251c7e0fef8db bpf_prog_3c8251c7e0fef8db [Percent: local period]
> > 45.05 push %rbp
> > 0.02 mov %rsp,%rbp
> > 0.03 sub $0x8,%rsp
> > 22.09 push %rbx
> [...]
> >
> > Do you see any issues with this data? With mitigations ON push %rbp and push %rbx overhead seems to
> > be pretty high.
> That's sample skid from the retpoline thunk when entring the XDP
> program. Pretty expensive push otherwise! :-)
> Another thought; Disclaimer: I'm no spectrev2 expert, and probably not
> getting the mitigations well enough. So this is me trying to swim at
> the deep end! Would it be possible to avoid the retpoline when
> entering the XDP program. At least for some XDP program that can be
> proved "safe"? If so, PeterZ's upcoming static_call could be used from
> the driver side.
Alexei, Jakub
Do you think it will be possible to avoid this overhead when mitigations are turned ON?
The other part of the overhead is going through the redirect path.
Can i assume that your silence as an indication that you are now okay with optional bypass
flag as long as it doesn't effect the normal XDP datapath. If so, i will respin and submit
the patches against the latest bpf-next
-Sridhar
Powered by blists - more mailing lists