On 04/01/2015 03:20 PM, Stephen Smalley wrote: > On 04/01/2015 02:58 PM, Ravi Kumar wrote: >> Hi Team , >> In reference to old discussion via the mail thread , >> http://marc.info/?l=selinux&m=140387478632108&q=raw >> >> This is on the context on removing the synchronize_net() from bootup and >> was concluded with optimization on reducing the the number of call to >> synchronize_net() In context to to this what we are seeing is skipping >> the call is saving much time on android bootup and based on the >> discussion at least for android systems it look like we can still >> skip this call as suggest in the initial patch which is much saving on >> the bootup time . But still i dont see any mainline / signed off sort >> of patch for andriod or any one using this . Did we see any issue or >> planned different . >> >> At least on KK the bootup time was under control for L code base we are >> trying to see all the ways of optimization any input are greatly >> appreciated. > > commit 615e51fdda6f274e94b1e905fcaf6111e0d9aa20 > Author: Paul Moore <pmoore@xxxxxxxxxx> > Date: Thu Jun 26 14:33:56 2014 -0400 > > selinux: reduce the number of calls to synchronize_net() when > flushing cache > > When flushing the AVC, such as during a policy load, the various > network caches are also flushed, with each making a call to > synchronize_net() which has shown to be expensive in some cases. > This patch consolidates the network cache flushes into a single AVC > callback which only calls synchronize_net() once for each AVC cache > flush. > > Reported-by: Jaejyn Shin <flagon22bass@xxxxxxxxx> > Signed-off-by: Paul Moore <pmoore@xxxxxxxxxx> And this was uploaded to the Android kernel/common tree along with various other SELinux kernel fixes/improvements, see https://android-review.googlesource.com/#/q/owner:sds+project:kernel/common _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
