Jakub Kicinski writes:
> On Mon, 18 Jan 2021 16:40:21 -0800 Vinicius Costa Gomes wrote:
>> + == ==
>> + ``ETHTOOL_A_CHANNELS_HEADER`` nested request header
>
> ETHTOOL_A_PREEMPT_HEADER
>
>> + ==
On Mon, 18 Jan 2021 16:40:21 -0800 Vinicius Costa Gomes wrote:
> + == ==
> + ``ETHTOOL_A_CHANNELS_HEADER`` nested request header
ETHTOOL_A_PREEMPT_HEADER
> + == ==
Hi Vladimir,
Vladimir Oltean writes:
> On Mon, Jan 18, 2021 at 04:40:21PM -0800, Vinicius Costa Gomes wrote:
>> +int ethnl_set_preempt(struct sk_buff *skb, struct genl_info *info)
>> +{
>> +struct ethnl_req_info req_info = {};
>> +struct nlattr **tb = info->attrs;
>> +struct ethtool_
On Mon, Jan 18, 2021 at 04:40:21PM -0800, Vinicius Costa Gomes wrote:
> +int ethnl_set_preempt(struct sk_buff *skb, struct genl_info *info)
> +{
> + struct ethnl_req_info req_info = {};
> + struct nlattr **tb = info->attrs;
> + struct ethtool_fp preempt = {};
> + struct net_device *
Frame preemption (described in IEEE 802.3br-2016) defines the concept
of preemptible and express queues. It allows traffic from express
queues to "interrupt" traffic from preemptible queues, which are
"resumed" after the express traffic has finished transmitting.
Frame preemption can only be used
