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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHA+R7M1wYwLA32fw=jzOUTR1+_zy8K9ugJohLmv1Tr1UHdhTw@mail.gmail.com>
Date:	Thu, 9 Jan 2014 16:44:41 -0800
From:	Cong Wang <cwang@...pensource.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	David Miller <davem@...emloft.net>,
	netdev <netdev@...r.kernel.org>,
	Neal Cardwell <ncardwell@...gle.com>,
	Jerry Chu <hkchu@...gle.com>
Subject: Re: [PATCH net-next] net: gro: change GRO overflow strategy

On Thu, Jan 9, 2014 at 2:12 PM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> +               /* locate the end of the list to select the 'oldest' flow */
> +               while (nskb->next) {
> +                       pp = &nskb->next;
> +                       nskb = *pp;
> +               }
> +               *pp = NULL;
> +               nskb->next = NULL;

How long could this list be?

I think it's time to use doubly linked list for gro,
although definitely not in this patch.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ