私の名前はつぎかずしばとNACで仕事をしています東京で昨日の夜12時間の長い旅に来ました長い旅に来ましたでもこのお昼に楽しみですとても良いコンフレンズです今日のLTSIプロジェクトで働いています3つの紹介をしたいと思います1つはカーネルスタティスティックス・プロセスそしてLTSIのストーリーそして6年間のレッスンをしていますそしてロングアタムのカーネルスタティックスを続けます今日のLTSIプロジェクトで働いていますまた私はシュバターです私はLTSIプロジェクトで働いていますそしてLTSIとLTSIのアドブーケットでLTSIとLTSIを使ってリアルプロダクトとリアルプロダクトの使用をしていますそしてリアルプロダクトで働いていますそしてリアルプロダクトで働いています2.4年間のリアルプロダクトで働いていますリアルプロダクトは最も成功なオープンソースプロジェクトですそして26年間のプロジェクトで働いています新たなアダプションで働いていますエンタープライズ、クラウド、ネブワーク、スマートフォン、ロボティックス、IOT、いろいろいろなものを使ってGPRV2を使ってみんなのコードを share the code for everyoneRenax is developed by the community and for every year, every release,1,700 people are participating230 companies are working for Renaxupstream for every releaseand growing every year1.5 million lines of code4,000 files are increased26 years of history, so long yearsso that lots of maintainers have a great skillto manage the subsystemand they have a professional knowledge of its area of technologiesso these kind of great technology placesonly in the open source and Renax is only the placeand here's the status of Renax kernelRenax releases 4.13and that was released in September 3rd this yearand 24 mega lines of code596 lines were increased from 4.12last onethe files were 60,000and 700 files were increased from last releaseand this development cycle was just 63 daysthat was released since 4.2 kernel was releasedand also current stable kernel is 4.13.9and current development kernel is 4.14-rc5I will try to explain some more details about thisso how many of days the kernel were developedI was count each versionfor the older one, 2015it was 5 version were releasedand mostly 60x days are spentand in the 2016it's also 60 days and sometimes it's 70 daysand 6 release was happenand for this yearright now it's 4.14 is not yet releasedbut maybe this one will be released in Novemberso 5 release in this yearand mostly longer one is 80 daysbut 60 or 6363 days means 9 weeksand 70 days means 10 weeksmost of the release will happen on Saturday on Sundayso 10 weeks or 9 weeksthat means 63 days or 70 daysand as you already knowthat Linux kernel is development is happeningin the just latest releasethe upstream includes newer patchesand also fixesonly the place changes the kerneland that patches are reviewed by the skilled maintainersand tested with other proposersto confirm without any conflictand well coordinated development processfor over thousands of developersthat's the kernel developmentand this is a picture of howthe kernel is developingjust after release of 4.10two weeks of merge window will happeneveryone can propose the newer patchesfor the merge windowand after thatdashrc1 will be releasedand the number of timesof release candidate will happenthat is the stabilisation phaseand mostlydashrc7 or 6then the newer kernel will be releasedand that will take 9 weeksor 10 weeksand that means 63 days and 70 daysand here is a graph of howLinux kernel source code is growingand 4.13 is nearlyabout 25M linesand most probably15M will be over 25Mof lines of codeyou caneasy to understandconstantly growing the source codeand Linux is a really a rapid release cyclethere are more than 5 times of chanceto merge the code into upstreambut other project maybe 6 months release cyclemeans that 2 times of chancefor the developers a lot of chanceto merge the new code into upstreambut on the other handfor the production usageso many chance to use newer kernelto use productionand that needs more deeper knowledgeto pick a right versionthat is a kind of issue for productionbut I will try to explainbut more other chanceto use a more better versionone is a stable kernelthat is recommended for userswho want the most recent stable kerneland 4.10.1234but this lifetime is justthe next version will be releasedthis one is not so much usefulfor the production usebut people who wanted the latest versionbut without the experimental featurethat will be okayhere islet's get back the latest datathe latest release is 4.13and the stable kernelis 4.13.7it's 7 times for a stable versionand the development versionis 4.14-RC5that is a yellow circleand the dash RC maybe 6 or 7then 4.14 will be releasedthat is the current latest situationand for the peoplewho wanted to use more longer term usagefor the kernelthat is LTSlong term stable kernelthat is extended maintenance periodof stable kerneland the kernel to continue to back portthe bargain security fixto the single kerneland this one will be pickedone version per yearand maintained 2 yearsthis one will be much betterthan the stable kerneland the latest upstream versionfor the production usageso that people understandthis value of this onetrying to use LTSfor the real productionand why LTSthis is only the treeto get fix from the communityand in the real use casetested and conformed kernelthat is really importantless importance for newer featuresnew experimental featuresand fix will be released a number of timesand should be applied frequentlybecause of our security and bug fixshould be provided to the customersand bugs funding LTSshould be reported back to communityand fixed in upstreamand then back ported to LTSso what kind of LTS version is existingyou can see this URLit's a kernel.orgI was copied this onemost bottom portion 3.2is maintained by Ben Hatchingit was released in 2012for the purpose of dbm maintainingand it was 6 yearscommitted to maintainand 3.10 is maintainedby William Taryufor his own kernel releaseand 3.16 is maintainedby Ben Hatchingalso for the dbm kernel4.1 is maintained by Sasha Revinfor he is working for somecarrier company to maintainthat purposeand 4.4 and 4.9 ismaintained by Greg HartmanFellow of the Linux Foundationis a nearly neutral positionand 4.4 isreleased in 2016and it was maintained for 2 yearsso that become the end of lifemaybe next yearbut just recently announcedthat it will expand it 6 yearscommitted to 2020until 2020that will be maintainedand 4.9 isreleased in 2016last yearand continue to maintain2019this is a 2 years termso how many fixwill be providedfor each of the kernelsyou can see a red one is LTSblack one is just stableso black one stable versionis providedless than thousands of fixesbecause of about 2063 or70days period of time to maintainbut the latest LTS4.9 is now4800 of fixes are providedthat was shownin the latest upstream fixesand then getbackported to 4.9this one will be really importantlet's see another version4.4 is 5600and 4.1 is 4000316 is 7000 of fixesprovidedthis is a differencebetween LTS and another kernelsso this one will be really useful forproduction usageand how many fixes, yearly fixesI was also countedfor 4.9and 4.4is really maintainedpoint 8 yearsand total commits were 4000so yearly 4000and 4.4is took 1.8 yearsso that yearly 3000so that others are also 22000that's the value of using LTSthese patches can be appliedour own productthat's the value of LTSso I'm working for LTSIso what is LTSIthis is an open source community to createand maintain LTSI kernel for long termthis is based on LTSthis patches can be appliedand also add another chanceto include further patches on top of LTSthis is LTSIbecause of LTSjust only provided and not be able toadd on top of LTS are newer featuresbut we will try to provide more chanceto latest features on top of LTSthat is more useful for using productionand also we areindustry party to share the best practiceand help companies to use Linux for longer termso we are discussing with other companiesand other project towanted to use Linux kernel formore longer termhere is a picture of how the difference between LTSand LTSIthe most bottom part is LTSrelease one version per year are maintainedand frequently large number of fix providedbut on top of LTSwe are providing help developers for upstreamand all test frameworkthat is done by a team boardand huge testing by contributorsbecause of LTSI is joined bysome of our companies wanted to more testingthe test result will be shared on top of LTSIthat is another valueand share status information provideda problem among the industry peoplethat we will provide a chance todiscussing each other how the problem has happenedand how it was solved by each companythat is another value of LTSIand be able to addrequired feature on top of LTSthat real patch merge chance for LTSon top of LTSwe started LTSI projectfirst presentation was happened in6 years ago, 2011 in Praguethis place, so now it's a 6 years timeand we have startedstable kernel for androidin 2011that was a time ofvery early stage of androidand every Android release was useddifferent kernel with a 6 months release cycleso the hand set manufacturers are really hardto use the latest kernelany other SOC vendors patchesand also some add-on patches from Googleso that we really wanted to usestable kernel and use a longer termin that time it was a time ofandroid 3.0, ice cream sandwichit was used Linux kernel 3.0we were started tostabilize Linux kernel 3.0as I mentioned number of differentcarnity like SOC dependent patchesand also Google dependent patchesand also in-house patchesshould be merged into the single kernelthat was so hardthat's the initial statusand we have a number of discussionabout the shape of LTSrelease every yearwas that happen in that discussionbecause of maintainernow maintainer is Greg Hartmanhe needs to maintainmaybe yearly release andafter 3 years he shouldmaintain 3different kernelif it expands more thenmore large number of kernelthat is one thingand also Google wasreleased every 6 months a different kernel versionso that 2 years maybe a reasonable timeand for both companiesand also maintainers point of viewbut right now every people wanted to usemore longer term and also Google is trying tobe able to uselonger lifefor the same kernelso the situation becomes differentso that maybe it will be a chance to changethe 2 years maintaining timeand also every year releaseand this one is the last onemaintain 2 LTS kernel is reasonable for that timeand another history isGreg is maintainer of LTSand also LTSIand we were released at 3.0, 3.4and these kind of kernelfor mostly yearly pacesand the latest one is 3, 4.9 LTSIwere already released inearly septemberone is also integrated with YOKTO projectin 2012YOKTO is already usedmany of embedded productsabout 60% of shareso that you are able to useYOKTO and also LTSIthat is the current situationand we have had workshop and sessiondiscussion issue among the industryand have many of use caselike AGL or some other embedded productsOK lessons learned in 6 yearsI would like to present 3 thingsLTS and LTSI is only a choicefor products and upstream fast policyand security and bug fix issuefor long term usage LTSLTSI is just fit as I explainedby statisticsLTSI provides2 to 3,000 purchase in a yearthat work should be done by a single companythat company needs a specific resourcejust not only the resource but alsothe maintainer should havedeep knowledge of broad range of Linux kernelso that makes so hardbut using LTSI is really easyand now all the Android devicesusing LTSI as I checked outmost of the majorhand set manufacturers kernel releasemost of the Android is using a stable kerneland so LTSI is a default choicefor the other use casesand there is more longer term requirementsCIP is a civil infrastructure platformwanted to use more than 10 yearsmaybe 15 years of usageand AGL alsoautomotive-grade Linux also wanted to use more than 10 yearsand Androidlastly statedOS update for 2 yearsand security fix for after 3 yearsso that makes 5 years term oflifetime of Androidso such use case LTS and LTSIwill be just fit for the requirementand upstream fast policymaybe 6 years agochange in kernel for production firstthat makes problem for long term use casebecause large number of fixmay not applicable in the futurebecause of the several thousand patch from communitybased on the vanilla kernelif the production firstand the developer change some variety of portionthen the patch cannot be able toapply so thatupstream fast policy is really importantand huge discussion happened before kernel summit last yearcompanies wanted to add on top of LTSsome other in-house patchesbut after the huge discussion happenedupstream fast policy is really importantfor long term use caseso that's why companies developer needparticipate in Linux kernel communitiescompanies own change should bemore into upstreamthat is upstream fast policyand back ported to LTSand the way to use kernel long termbut for that initial hard to join the communityfor the company's developermaybe high but really it's really importantto use kernel as a long termand LTSI is keeping upstream fast policyso that most of the LTSI patchshould be merging the later upstreamand then back ported to on top of LTSthat is upstream fast policyand security and bank fixeslook back in 60 years agosecurity and bank fix may not so much importantjust people shipping onlybut right now fixing the problemis a mandatory requirementand the community provided fixesthat base code should be same as upstreamso otherwise immediate patch releasewill not possibleso that's another reason whybase code should be same as upstream codeso that in-house patchesmust be as small as possiblethat was lessons around in 6 yearsand let's go tofurther step of maintaining kernel long termI was explainedhistory or 6 years look backand let's golet's see in the futurenear futureone isI would like to point outis a project travelfor android projectthat is try to isolate android OSand hardware specific codethere is avendor specific binderslash devpnd binderall the vendor specific kernel codeis working under this binderand withvendor test suitesand compatibility test suitesthat will test its interfaceso that that will completely separatevendor implementationand operating systemby this changesericon specific patchand LTS patchcan be separatedseparatelyseveral thousands of LTS patchshould be appliedbut separatelyvendor specific patchesthat meansonce we haveseveralhand setusingdifferent hardwarebutvendor specific portion is just onlyblack oneso that that one is separatedso that all the upper layernot necessary to testingthat is the value ofproject traveland also LTS patchesprovided thousands of patchesthen that isjust should be testedin a singlemaybe single platformnot necessary totesting on top of anotherhardware platformthat is the value ofproject travelanother point is live patchingthis is just an enterprise portionfeature of live patchingcarnel code was mergedsincerenex 4.0that was the result ofsuce kgraphedand read that fromkpatchesthat this technologyis patching the kernelis runningcurrent running kernelcan be patcheddynamicallyso the mostsuprisebut it'ssevering on x86most of the peopleyou may be usingarm butthis one is possibleto applyimmediate patchingand without downtimeby using this livepatching some superimportant patch can beapplied without downtimeそして、カーネルアップデートのメカニズムは、コアOSやクロームOSにおいて、2つのポジションがあります。Aはコーネットを行って、Aはコーネットを行って、新カーネルをパーティションBに移動することができます。新カーネルをパーティションBに移動することができます。Googleはオマハのオープンソースについて、セキュリティリーゾンについて、新カーネルをパーティションBに移動することができます。カーネルをアップデートすることができます。参考に対することができます。それについて、技能が運営できると回すことができることができます。新カーネルをパーティションBに移動することをカーネルをオーテイン防御者の所に返せます。コンテーナーはパッケージの技術を使うことができますコンテーナーは、一番上手なプロベームのライブラリーとランリーのプロセッサーのバージョンですオーエアの一つのライブラリーはバージョンはクレイし、コンテーナーで使うことができるためにライブラリーはコンテーナーで使うことができますオーエアの一つのライブラリーとランリーのプロセッサーのバージョンはパイソン、ルビーなどのプロセッサーのバージョンですでも、コンテーナーを使うことができますオーエアの一つのライブラリーはコンテーナーで使うことができますウェンソフトが使えるためにオーエアの一つのライブラリーはランリーの一つのプロセッサーのバージョンはコンテーナーで使うことができるためにこのオーエアを使うことができるためにこのオーエアは、コンテーナーで使うことができますこのオーエアの一つのパイソンは分量されているのでコンテイナーOSは違うことが必要となりますこれが少し難しいですが未来の必要が必要となりますこれが私の説明ですここはDCSデブロックメントフランLTSI-4.9をリリースしていますアリース・セプテンブルこのメントフランはYokuto 2.4をリリースしていますAGLガイズはYokuto 2.4を使ってダーリン・ダブリリースを使ってダブリリースのストリームラインを使ってこれが明日のフランです4.14はLTSI-4を使ってDCSデブロックメントフランを使ってそして6月の時間を待つことができます4.15の自分のパッチをごめんなさい15、16、17ごめんなさいこの6月のフランを上にLTSI-4を使ってDCSデブロックメントフランを使ってLTSI-4を使ってLTSI-4を使ってLTSI-4を使ってこのパッチを使ってそしてYokutoYokutoとAGLバージョンこれがフランの誕生日のメールリストをご紹介する今後のフランのフランのこれが私の誕生日の4.94.14の長い時間を増やすことができますでも今後は誕生日のメンテナーの仕事が多くなりますでも今後はFuegoやRenaroが多くのもっとエフィシャントでLTSI-4が長い時間を増やすことができますでも待ちましょうそれをよくよくフレーマークを作ることができますそれが長い時間をLTSI-4が提供することができますそれが私のプレゼンテーションですそれが結局LTSI-4はコミュニティとインタストリーションででもでもコミュニティとコミュニティとオープンソースで非常に重要ですLTSI-4はメーリングリストでリナックスファンデーションのコンフランスですありがとうございますちょっとちょっとちょっと問題はどうぞどうぞそのプレゼンテーションはLTSI-4はアップストリーマークを作ることができますどんなプレゼンテーションかLTSI-4はコミュニティとオープンソースでLTSI-4の點をスピードしてアップストリーマークをコーディアのコンプリの会社のコーディアンの中でこのようなパチを持っているからアップスタイムのパチを送りアップスタイムのデブロープリンに関係はないタイムの伺いだとまた、このマンテイナーに来てもらってくれるこれに助けてくれるこれからの支援を受けますok anything else yes please sorry i could not hear you microphone is over there i'm sorry thank youyeah pram team pram pram topt patch in the lts relationship is at least your questionyeah actually we are discussing a number of times how we will be able to merge oralign pram to rt and lts but now renas is not yet accept the pram to rt we are upstream fast policyso that unfortunately it's not yetaligned but i think pram to rt is trying to aligntrying to provide their patch as the same as lts version soah if people wanted to use pram rt with lts then that will be possible that iscurrent situation is this answer for your question okay thank you so it's time thank you so much