Re: ip_fragment ip6_fragment

2021-02-27 Thread Vitaliy Makkoveev
> On 26 Feb 2021, at 14:08, Alexander Bluhm wrote: > > Hi, > > I always bothered me that ip_fragment() and ip6_fragment() behave > sligtly differently. Unify them and use an mlist to simplify the > fragment list. > > - The functions ip_fragment() and ip6_fragment() always consume the mbuf.

Re: ip_fragment ip6_fragment

2021-02-26 Thread David Gwynne
I like it. I would like it more if you named the mbuf list variable "fml". ok by me. > On 26 Feb 2021, at 9:08 pm, Alexander Bluhm wrote: > > Hi, > > I always bothered me that ip_fragment() and ip6_fragment() behave > sligtly differently. Unify them and use an mlist to simplify the > fragment

ip_fragment ip6_fragment

2021-02-26 Thread Alexander Bluhm
Hi, I always bothered me that ip_fragment() and ip6_fragment() behave sligtly differently. Unify them and use an mlist to simplify the fragment list. - The functions ip_fragment() and ip6_fragment() always consume the mbuf. - They free the mbuf and mbuf list in case of an error. - They care abou