From: Nicolas Schichan <nschichan@freebox.fr>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Cong Wang <amwang@redhat.com>
Subject: Re: freeze with interface rename & SIOCGIFNAME
Date: Tue, 25 Jun 2013 19:12:43 +0200 [thread overview]
Message-ID: <51C9CF8B.6030502@freebox.fr> (raw)
In-Reply-To: <1372179933.3301.106.camel@edumazet-glaptop>
On 06/25/2013 07:05 PM, Eric Dumazet wrote:
> On Tue, 2013-06-25 at 09:57 -0700, Eric Dumazet wrote:
>
>> I am not sure it's needed, because the writer holds a spinlock and is
>> not allowed to sleep or being preempted.
>>
>> If it's needed, there is a bug somewhere else...
>
> Oh well, its a write_seqcount, so no spinlock...
That's what I was going to reply.
Am I right in thinking that the process spinning on SIOCGIFNAME should be
naturally be preempted by other tasks by the scheduler once its timeslice has
expired or am I missing something ?
--
Nicolas Schichan
Freebox SAS
next prev parent reply other threads:[~2013-06-25 17:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51C9BB9C.4050405@freebox.fr>
2013-06-25 16:15 ` freeze with interface rename & SIOCGIFNAME Eric Dumazet
2013-06-25 16:27 ` Nicolas Schichan
2013-06-25 16:57 ` Eric Dumazet
2013-06-25 17:05 ` Eric Dumazet
2013-06-25 17:12 ` Nicolas Schichan [this message]
2013-06-25 17:19 ` Eric Dumazet
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=51C9CF8B.6030502@freebox.fr \
--to=nschichan@freebox.fr \
--cc=amwang@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.