[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9235D6609DB808459E95D78E17F2E43D404CC166@CHN-SV-EXMX02.mchp-main.com>
Date: Mon, 21 Mar 2016 18:42:06 +0000
From: <Woojung.Huh@...rochip.com>
To: <stern@...land.harvard.edu>, <oneukum@...e.com>
CC: <geert@...ux-m68k.org>, <UNGLinuxDriver@...rochip.com>,
<davem@...emloft.net>, <linux@...ck-us.net>, <rjw@...ysocki.net>,
<netdev@...r.kernel.org>, <linux-usb@...r.kernel.org>,
<linux-pm@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] lan78xx: Protect runtime_auto check by #ifdef CONFIG_PM
> But this leaves open the issue that querying the device too often will
> prevent it from going into autosuspend. It seems to me that the best
> way to deal with this is to make sure that the autosuspend timeout is
> shorter than the interal between queries, not to make the querying
> conditional on !runtime_auto.
Short autosuspend timeout can affect performance. For instance our experiments showed that
shorter than 10sec timeout made Ethernet performance degrade because of wakeup delays.
So, just putting shorter timeout may have some side effects.
Woojung
Powered by blists - more mailing lists