Thanks a lot for the .config file.
I also tested it, with mdio-bus.o in the Makefile, glad to got that there is
no problem of that, although I don't know the reason/trick yet.
On Wed, Jan 06, 2021 at 04:13:56PM -0800, Florian Fainelli wrote:
> The change was done on purpose, and your patch does no
now how.
Signed-off-by: Zhi Han
---
drivers/net/phy/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/phy/Makefile b/drivers/net/phy/Makefile
index a13e402074cf..0840e9055b5a 100644
--- a/drivers/net/phy/Makefile
+++ b/drivers/net/phy/Makefile
@@ -15,7 +
On Sun, Jul 26, 2020 at 6:42 AM Willem de Bruijn
wrote:
>
> On Sat, Jul 25, 2020 at 7:08 PM Han wrote:
> >
> > My apologies if this is not the right place to ask this question.
> >
> > I'm trying to use UDP GSO to improve the throughput. My testing shows
&g
on]
$ ethtool --show-offload wlan0 | grep -i udp-segment
tx-udp-segmentation: off [fixed]
A quick try did not work:
$ sudo ethtool -K wlan0 gso on
Could not change any device features
My test hardware is Raspberry Pi 4, and the Linux kernel version is
4.19. My test program is in C.
Thanks.
Han
On 6/15/07, Kieran Mansley <[EMAIL PROTECTED]> wrote:
The lock protects the use_count variable. The use_count variable
prevents the plugin module unloading while it is being used. I couldn't
just use the lock to prevent the module unloading as the hook function
(i) might block (and holding a s
Hi, Kieran,
I'm just wonder why you try to acquire the lock and increase the
hooks_usecount each time when you use the hook routine. Is there any
generic ways to synchronze the code path using hook routines and
netfront_accelerator_unloaded, considering you can synchronize the
tx/rx data path eas
