lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <029601da233d$d4b8a9a0$7e29fce0$@trustnetic.com> Date: Thu, 30 Nov 2023 11:32:22 +0800 From: Jiawen Wu <jiawenwu@...stnetic.com> To: "'Andrew Lunn'" <andrew@...n.ch> Cc: <netdev@...r.kernel.org>, <davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>, <pabeni@...hat.com>, <linux@...linux.org.uk>, <horms@...nel.org>, <mengyuanlou@...-swift.com> Subject: RE: [PATCH net-next 2/5] net: wangxun: add ethtool_ops for ring parameters > > +int wx_set_ring(struct wx *wx, u32 new_tx_count, u32 new_rx_count) > > +{ > > + struct wx_ring *temp_ring; > > + int i, err = 0; > > + > > + /* allocate temporary buffer to store rings in */ > > + i = max_t(int, wx->num_tx_queues, wx->num_rx_queues); > > + temp_ring = vmalloc(i * sizeof(struct wx_ring)); > > So it is O.K. for the pages to be scattered around the physical > address space, not contiguous. Does this memory ever get passed to the > hardware? No, this memory is only used to temporarily store ring info. It will be freed after restoring the ring info.
Powered by blists - more mailing lists