From: pritambankar1988@gmail.com (Pritam Bankar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: What is RTNL lock?
Date: Mon, 28 Nov 2011 13:05:39 +0530 [thread overview]
Message-ID: <004601ccada0$56352d80$029f8880$@gmail.com> (raw)
In-Reply-To: <CALJfu6PWD1=Z4pCEpYxq+fzhJBeCHibmaVX7OzxuS83FqfZTCg@mail.gmail.com>
Hi,
http://lists.openfabrics.org/pipermail/general/2008-July/052458.html
This might help you.
From: kernelnewbies-bounces@kernelnewbies.org
[mailto:kernelnewbies-bounces at kernelnewbies.org] On Behalf Of rohan puri
Sent: 28 November 2011 12:36
To: Vimal; kernelnewbies
Subject: Re: What is RTNL lock?
On Mon, Nov 28, 2011 at 12:19 PM, Vimal <j.vimal@gmail.com> wrote:
Hi Rohan
Yes, I understood this part, but I am wondering what is the purpose of
this lock. I am guessing it's to protect all network related
operations from critical events, for e.g.: protecting a packet
transmit during device removal, protecting routing table entry during
route lookup, etc., but I can't find its precise documentation
anywhere. Thanks,
On 27 November 2011 22:44, rohan puri <rohan.puri15@gmail.com> wrote:
>
>
> On Sun, Nov 27, 2011 at 10:37 PM, Vimal <j.vimal@gmail.com> wrote:
>>
>> Hi all,
>>
>> In the Linux networking code, I see a lot of comments that say "Must
>> be called with RTNL lock."
>>
>> What is this lock? I tried searching for it but couldn't find any
>> explanation on what it is...
>>
>> Thanks
>> --
>> Vimal
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
> Hello Vimal,
> This is a mutex named rtnl_mutex. Refer file net/core/rtnetlink.c
> static DEFINE_MUTEX(rtnl_mutex);
>
> void rtnl_lock(void)
> {
> mutex_lock(&rtnl_mutex);
> }
> EXPORT_SYMBOL(rtnl_lock);
> Where ever you see those comments indicate that this mutex is to be held
> before execution of that code path.
> Regards,
> Rohan
--
Vimal
This lock is used to serialize changes to net_device instances from runtime
events, conf changes
Refer book understanding Linux network internals for more details.
Regards,
Rohan Puri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20111128/36231e74/attachment-0001.html
prev parent reply other threads:[~2011-11-28 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 17:07 What is RTNL lock? Vimal
[not found] ` <CALJfu6O_njezhzH0By3_2tVDN8wpyCyCxebJR-gQFgK+NJKkQg@mail.gmail.com>
[not found] ` <CAK3Ji10gW0iTSpnskkULDkRZTXorBjYzkTFPtYs-cE637FriyA@mail.gmail.com>
2011-11-28 7:05 ` rohan puri
2011-11-28 7:35 ` Pritam Bankar [this message]
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='004601ccada0$56352d80$029f8880$@gmail.com' \
--to=pritambankar1988@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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).