| To: | Mitchell Blank Jr <mitch@xxxxxxxxxx> |
|---|---|
| Subject: | Re: synchronize_net()? |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Sat, 13 Sep 2003 19:09:40 -0700 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20030913034611.GA83212@xxxxxxxxxxxxxx> |
| References: | <20030913034611.GA83212@xxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 12 Sep 2003 20:46:11 -0700
Mitchell Blank Jr <mitch@xxxxxxxxxx> wrote:
> /* Synchronize with packet receive processing. */
> void synchronize_net(void)
> {
> might_sleep();
> synchronize_kernel();
> }
>
> The "might_sleep()" isn't needed
As a matter of taste and ease of debugging it could be.
I think it's logical to place the might_sleep() calls as high
up in the call chain as is reasonable. This is especially true
for important oft-used interfaces for a subsystem.
In this way, you don't risk so much having a hard to decode backtrace
that misses the true culprit sleep'able call.
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH 8/10] [bonding 2.6] Enhance netdev notification handling, Amir Noam |
|---|---|
| Next by Date: | Re: ipt_physdev.c alignment problems on parisc64, David S. Miller |
| Previous by Thread: | synchronize_net()?, Mitchell Blank Jr |
| Next by Thread: | [IPV4] convert proc/net/pnp to seq_file., YOSHIFUJI Hideaki / 吉藤英明 |
| Indexes: | [Date] [Thread] [Top] [All Lists] |