netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mihai Maruseac <mmaruseac@ixiacom.com>
To: Mihai Maruseac <mihai.maruseac@gmail.com>
Cc: <dbaluta@ixiacom.com>, <mmaruseac@ixiacom.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"eric.dumazet@gmail.com" <eric.dumazet@gmail.com>,
	"mirq-linux@rere.qmqm.pl" <mirq-linux@rere.qmqm.pl>,
	"therbert@google.com" <therbert@google.com>,
	"jpirko@redhat.com" <jpirko@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dev: use ifindex hash for dev_seq_ops
Date: Wed, 12 Oct 2011 12:59:23 +0300	[thread overview]
Message-ID: <1318413563.2231.1.camel@sirius> (raw)
In-Reply-To: <1318413446-22258-1-git-send-email-mmaruseac@ixiacom.com>

On Wed, 2011-10-12 at 02:57 -0700, Mihai Maruseac wrote:
> Instead of using the dev->next chain and trying to resync at each call to
> dev_seq_start, use the ifindex, keeping the last index in seq->private field.

Please consider only my last patch email, the first one was missing
Signed-off-by line.

Thanks,
Mihai

  reply	other threads:[~2011-10-12  9:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 15:20 [PATCH] dev: use name hash for dev_seq_ops Mihai Maruseac
2011-10-07 16:24 ` Stephen Hemminger
2011-10-08  7:22   ` Mihai Maruseac
2011-10-10  8:43   ` Mihai Maruseac
2011-10-11  5:55     ` Stephen Hemminger
2011-10-12 10:08       ` Mihai Maruseac
2011-10-12  9:49 ` [PATCH] dev: use ifindex " Mihai Maruseac
2011-10-12  9:57 ` Mihai Maruseac
2011-10-12  9:59   ` Mihai Maruseac [this message]
2011-10-12 15:50   ` Stephen Hemminger
2011-10-14 12:20     ` Mihai Maruseac
2011-10-14  9:53   ` Mihai Maruseac
2011-10-14 12:53     ` Eric Dumazet
2011-10-17  8:03       ` Daniel Baluta
2011-10-17 15:12         ` Stephen Hemminger

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=1318413563.2231.1.camel@sirius \
    --to=mmaruseac@ixiacom.com \
    --cc=davem@davemloft.net \
    --cc=dbaluta@ixiacom.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jpirko@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihai.maruseac@gmail.com \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=netdev@vger.kernel.org \
    --cc=therbert@google.com \
    /path/to/YOUR_REPLY

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

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).