Re: [PATCH v3 5/7] rust: percpu: Support non-zeroable types for DynamicPerCpu

[Yury Norov <yury.norov@gmail.com>]

On Thu, Sep 04, 2025 at 01:26:07PM -0700, Mitchell Levy wrote:
> On Wed, Sep 03, 2025 at 06:19:25PM -0400, Yury Norov wrote:
> > On Thu, Aug 28, 2025 at 12:00:12PM -0700, Mitchell Levy wrote:

...

> > > +impl<T: Clone> DynamicPerCpu<T> {
> > > +    /// Allocates a new per-CPU variable
> > > +    ///
> > > +    /// # Arguments
> > > +    /// * `val` - The initial value of the per-CPU variable on all CPUs.
> > > +    /// * `flags` - Flags used to allocate an `Arc` that keeps track of the underlying
> > > +    ///   `PerCpuAllocation`.
> > > +    pub fn new_with(val: T, flags: Flags) -> Option<Self> {
> > > +        let alloc: PerCpuAllocation<T> = PerCpuAllocation::new_uninit()?;
> > > +        let ptr = alloc.0;
> > > +
> > > +        for cpu in Cpumask::possible().iter() {
> > 
> > In C we've got the 'for_each_possible_cpu()'. Is there any way to
> > preserve that semantics in rust? I really believe that similar
> > semantics on higher level on both sides will help _a_lot_ for those
> > transitioning into the rust world (like me).
> 
> I'm not sure I understand what you mean --- I believe the semantics
> should be the same here (`cpu` takes on each value in
> `cpu_possible_mask`). Could you please clarify?
> 

I mean:

        for_each_possible_cpu(cpu) {
                let remote_ptr = unsafe { ptr.get_remote_ptr(cpu) };
                unsafe { (*remote_ptr).write(val.clone()); }
                let arc = Arc::new(alloc, flags).ok()?;
                Some(Self { alloc: arc })
        }

Is it possible to do the above in rust?