public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed

From: Pavel Emelyanov <xemul@parallels•com>
To: David Miller <davem@davemloft•net>,
	Eric Dumazet <eric.dumazet@gmail•com>,
	"Eric W. Biederman" <ebiederm@xmission•com>,
	Linux Netdev List <netdev@vger•kernel.org>,
	Ben Hutchings <bhutchings@solarflare•com>
Subject: [PATCH net-next 0/5] Per-net and on-demand link indices (and related) v3
Date: Thu, 09 Aug 2012 11:52:00 +0400	[thread overview]
Message-ID: <50236C20.4050108@parallels.com> (raw)

Hi!

This set tries to summarize the recent discussion of making ifindices friendly
to checkpoint-restore and consists of:

1. Prepare hash function to non-unique ifindices
2. Allow for specifying the desired ifindex on net link creation
3. Make ifindex generation per-net
4. Simplify loopback device ifindex access


Changes since v2:

* The pointer hash mix routine is rewritten
* Put ifindex on struct net in a better place
* Fixed compatibility on veth peer device ifindex configuration

Changes since v1:

* Fixed a stupid mistake with a pointer bits shift
* Turned the netdev_hash_mix routine into the generic ptr_hash_mix one
* Added a comment describing why loopback index is always 1 after the patch

Thanks,
Pavel

next             reply	other threads:[~2012-08-09  7:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09  7:52 Pavel Emelyanov [this message]
2012-08-09  7:52 ` [PATCH 1/5] net: Dont use ifindices in hash fns Pavel Emelyanov
2012-08-09  7:52 ` [PATCH 2/5] net: Allow to create links with given ifindex Pavel Emelyanov
2012-08-09  7:53 ` [PATCH 3/5] veth: Allow to create peer link " Pavel Emelyanov
2012-08-09  7:53 ` [PATCH 4/5] net: Make ifindex generation per-net namespace Pavel Emelyanov
2012-08-09  7:53 ` [PATCH 5/5] net: Loopback ifindex is constant now Pavel Emelyanov
2012-08-09 23:18 ` [PATCH net-next 0/5] Per-net and on-demand link indices (and related) v3 David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50236C20.4050108@parallels.com \
    --to=xemul@parallels$(echo .)com \
    --cc=bhutchings@solarflare$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=ebiederm@xmission$(echo .)com \
    --cc=eric.dumazet@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox