netdev - Re: [PATCH net-next 2/2] openvswitch: Use lockless genl.

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] [day] [month] [year] [list]

Date:	Thu, 18 Apr 2013 14:24:41 -0700
From:	Pravin Shelar <pshelar@...ira.com>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, dev@...nvswitch.org, jesse@...ira.com
Subject: Re: [PATCH net-next 2/2] openvswitch: Use lockless genl.

On Thu, Apr 18, 2013 at 2:18 PM, David Miller <davem@...emloft.net> wrote:
> From: Pravin B Shelar <pshelar@...ira.com>
> Date: Thu, 18 Apr 2013 14:16:52 -0700
>
>> OVS locking was recently changed to have private OVS lock which
>> simplified overall locking.  Therefore there is no need to have
>> another global genl lock to protect OVS data structures.  Following
>> patch uses of lockless genl family for OVS.  This also allows
>> more granual OVS locking using ovs_mutex for protecting OVS data
>> structures, which gives more consurrencey.  E.g multiple genl
>> operations OVS_PACKET_CMD_EXECUTE can run in parallel, etc.
>>
>> Signed-off-by: Pravin B Shelar <pshelar@...ira.com>
>
> Three problems with this submission:
>
> 1) When you resubmit a patch that's part of a series, you must repost
>    the entire series.
>
> 2) When you post a new version of a patch, you must list (after the
>    "---" delimiter) what has changed in this version.
>
> 3) When you post a new version of a patch, you must indicate this by
>    putting "[PATCH v2 ...] ...", for example, in the Subject line.

I thought I just need to post patch that was changed. Let me send
updated series again.
--
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