mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Barker <paul.barker.ct@bp.renesas.com>
To: Sergey Shtylyov <s.shtylyov@omp.ru>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next v2 6/7] net: ravb: Enable SW IRQ Coalescing for GbEth
Date: Wed, 14 Feb 2024 09:29:49 +0000	[thread overview]
Message-ID: <d685bee8-c760-463b-ba72-6c6dda2cd96c@bp.renesas.com> (raw)
In-Reply-To: <7c28bbea-0b3f-ee62-05c8-e6f1bc738b0b@omp.ru>


[-- Attachment #1.1.1: Type: text/plain, Size: 1314 bytes --]

On 12/02/2024 20:40, Sergey Shtylyov wrote:
> On 2/12/24 2:45 PM, Paul Barker wrote:
> [...]
>>>> diff --git a/drivers/net/ethernet/renesas/ravb.h b/drivers/net/ethernet/renesas/ravb.h
>>>> index 55a7a08aabef..ca7a66759e35 100644
>>>> --- a/drivers/net/ethernet/renesas/ravb.h
>>>> +++ b/drivers/net/ethernet/renesas/ravb.h
>>>> @@ -1078,6 +1078,7 @@ struct ravb_hw_info {
>>>>  	unsigned nc_queues:1;		/* AVB-DMAC has RX and TX NC queues */
>>>>  	unsigned magic_pkt:1;		/* E-MAC supports magic packet detection */
>>>>  	unsigned half_duplex:1;		/* E-MAC supports half duplex mode */
>>>> +	unsigned needs_irq_coalesce:1;	/* Requires SW IRQ Coalescing to achieve best performance */
>>>
>>>    Is this really a hardware feature?
>>
>> It's more like a requirement to get the best out of this hardware and the Linux networking stack.
>>
>> I considered checking the compatible string in the probe function but I decided that storing a configuration bit in the HW info struct was cleaner.
> 
>    Yes, but you added the new bit under the "hardware features" commet. :-)
> 
>>>    Also, s/Requires SW/Needs software/ and s/to achieve best performance//,
>>> please...
>>
>> Will do.
> 
>    The comment is too long, I think. :-)

I'll fix both in the next revision.

-- 
Paul Barker

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3577 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2024-02-14  9:29 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06  9:19 [RFC PATCH net-next v2 0/7] Improve GbEth performance on Renesas RZ/G2L and related SoCs Paul Barker
2024-02-06  9:19 ` [RFC PATCH net-next v2 1/7] net: ravb: Simplify poll & receive functions Paul Barker
2024-02-10 16:13   ` Sergey Shtylyov
2024-02-06  9:19 ` [RFC PATCH net-next v2 2/7] net: ravb: Count packets instead of descriptors in RX path Paul Barker
2024-02-10 16:32   ` Sergey Shtylyov
2024-02-06  9:19 ` [RFC PATCH net-next v2 3/7] net: ravb: Always process TX descriptor ring Paul Barker
2024-02-10 16:39   ` Sergey Shtylyov
2024-02-06  9:19 ` [RFC PATCH net-next v2 4/7] net: ravb: Always update error counters Paul Barker
2024-02-10 16:46   ` Sergey Shtylyov
2024-02-06  9:19 ` [RFC PATCH net-next v2 5/7] net: ravb: Align poll function with NAPI docs Paul Barker
2024-02-10 17:10   ` Sergey Shtylyov
2024-02-06  9:19 ` [RFC PATCH net-next v2 6/7] net: ravb: Enable SW IRQ Coalescing for GbEth Paul Barker
2024-02-10 18:42   ` Sergey Shtylyov
2024-02-12 11:45     ` Paul Barker
2024-02-12 20:40       ` Sergey Shtylyov
2024-02-14  9:29         ` Paul Barker [this message]
2024-02-06  9:19 ` [RFC PATCH net-next v2 7/7] net: ravb: Use NAPI threaded mode on 1-core CPUs with GbEth IP Paul Barker
2024-02-10 19:00   ` Sergey Shtylyov
2024-02-10 19:36 ` [RFC PATCH net-next v2 0/7] Improve GbEth performance on Renesas RZ/G2L and related SoCs Sergey Shtylyov
2024-02-12 11:52   ` Paul Barker
2024-02-12 20:53     ` Sergey Shtylyov
2024-02-13  9:38       ` Sergey Shtylyov
2024-02-14  9:17       ` Paul Barker

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=d685bee8-c760-463b-ba72-6c6dda2cd96c@bp.renesas.com \
    --to=paul.barker.ct@bp.renesas.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=s.shtylyov@omp.ru \
    --cc=wsa+renesas@sang-engineering.com \
    --cc=yoshihiro.shimoda.uh@renesas.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

all inboxes | Powered by JetHome®