Re: [PATCH v2 net-next] udp: introduce __sk_mem_schedule() usage

[Jason Xing]

On Mon, Mar 6, 2023 at 10:51 PM Simon Horman <simon.horman@xxxxxxxxxxxx> wrote:
>
> On Mon, Mar 06, 2023 at 07:57:45PM +0800, Jason Xing wrote:
> > From: Jason Xing <kernelxing@xxxxxxxxxxx>
> >
> > Keep the accounting schema consistent across different protocols
> > with __sk_mem_schedule(). Besides, it adjusts a little bit on how
> > to calculate forward allocated memory compared to before. After
> > applied this patch, we could avoid receive path scheduling extra
> > amount of memory.
> >
> > Link: https://lore.kernel.org/lkml/20230221110344.82818-1-kerneljasonxing@xxxxxxxxx/
> > Signed-off-by: Jason Xing <kernelxing@xxxxxxxxxxx>
> > ---
> > V2:
> > 1) change the title and body message
> > 2) use __sk_mem_schedule() instead suggested by Paolo Abeni
> > ---
> >  net/ipv4/udp.c | 31 ++++++++++++++++++-------------
> >  1 file changed, 18 insertions(+), 13 deletions(-)
> >
> > diff --git a/net/ipv4/udp.c b/net/ipv4/udp.c
> > index 9592fe3e444a..21c99087110d 100644
> > --- a/net/ipv4/udp.c
> > +++ b/net/ipv4/udp.c
> > @@ -1531,10 +1531,23 @@ static void busylock_release(spinlock_t *busy)
> >               spin_unlock(busy);
> >  }
> >
> > +static inline int udp_rmem_schedule(struct sock *sk, int size)
>

> nit: I think it's best to drop the inline keyword and
>      let the compiler figure that out.

Thanks for the review. I'll do that in the v3 patch.

Jason