Kristof Hellwig, mbajt\u00ebsi i n\u00ebn-sistemit DMA, KVM, Slab Allocator dhe arkitektur\u00ebs PowerPC n\u00eb kernelin Linux, i cili n\u00eb nj\u00eb koh\u00eb ishte pjes\u00eb e komitetit t\u00eb menaxhimit teknik t\u00eb organizat\u00ebs Linux Foundation dhe kishte vepruar si padit\u00ebs n\u00eb nj\u00eb proces gjyq\u00ebsor lidhur me GPL ndaj VMware, refuzoi t\u00eb konfirmonte patch-et q\u00eb lidhen me mb\u00ebshtetjen e zhvillimit t\u00eb shofer\u00ebve n\u00eb gjuh\u00ebn Rust. Patch-et e propozuara shtonin blloqe mbi disa funksione t\u00eb n\u00ebn-sistemit DMA, duke lejuar p\u00ebrdorimin e DMA n\u00eb shofer\u00ebt n\u00eb gjuh\u00ebn Rust. <\/p>\n
Si arsye p\u00ebr refuzimin u p\u00ebrmend kompliksimi i p\u00ebrdit\u00ebsimit t\u00eb kodit p\u00ebr shkak t\u00eb mb\u00ebshtetjes n\u00eb gjuh\u00eb t\u00eb tjera dhe d\u00ebshira p\u00ebr t\u00eb ruajtur nd\u00ebrfaqet e programimit p\u00ebr DMA n\u00eb nj\u00eb form\u00eb t\u00eb lexueshme n\u00eb gjuh\u00ebn C, pa i mbivendosur ato me mb\u00ebshtetje t\u00eb paqart\u00eb. Christoph sugjeroi q\u00eb t\u00eb adresohet direkt n\u00eb API-n\u00eb origjinale C t\u00eb DMA n\u00eb \u00e7do driver n\u00eb gjuh\u00ebn Rust, p\u00ebr t\u00eb mos krijuar abstraksione t\u00eb tjera nga t\u00eb cilat do t\u00eb var\u00ebseshin mbajt\u00ebsit e b\u00ebrtham\u00ebs. <\/p>\n
Zhvilluesit e patch-eve njoftuan se do t\u00eb marrin p\u00ebrsip\u00ebr gjith\u00eb pun\u00ebn e mb\u00ebshtetjes s\u00eb kodit n\u00eb Rust, duke qen\u00eb t\u00eb gatsh\u00ebm t\u00eb mb\u00ebshtesin k\u00ebto patch-e vet\u00eb dhe duke e b\u00ebr\u00eb paketimin n\u00eb nj\u00eb n\u00ebn-dhak\u00eb (rust\/kernel\/dma.rs). N\u00eb p\u00ebrgjigje, Kristofo vendosi nj\u00eb veto (\u2018Nacked-by\u2019) ndaj pranimit t\u00eb patch-eve t\u00eb lidhura me Rust dhe theksoi se nuk kishte nevoj\u00eb p\u00ebr nj\u00eb mbik\u00ebqyr\u00ebs tjet\u00ebr. Kristofo deklaroi se n\u00ebse zhvilluesit e paketimit d\u00ebshirojn\u00eb t\u00eb arrijn\u00eb pamund\u00ebsin\u00eb e mb\u00ebshtetjes s\u00eb Linux-it p\u00ebr shkak t\u00eb p\u00ebrzierjes s\u00eb disa gjuh\u00ebve n\u00eb nj\u00eb baz\u00eb kodi, ata duhet ta b\u00ebjn\u00eb k\u00ebt\u00eb n\u00eb drayverin e tyre dhe jo ta shp\u00ebrndajn\u00eb k\u00ebt\u00eb tumor n\u00eb n\u00ebn-sistemet kryesore t\u00eb kernelit. <\/p>\n
Megjithat\u00eb, Kristof sqaroi se nuk ka asgj\u00eb kund\u00ebr gjuh\u00ebs Rust dhe e konsideron at\u00eb si nj\u00eb nga gjuh\u00ebt m\u00eb t\u00eb mira t\u00eb reja, por \u00ebsht\u00eb kund\u00ebr p\u00ebrzierjes s\u00eb kodit n\u00eb gjuh\u00eb t\u00eb ndryshme. Sipas Kristofit, ai \u00ebsht\u00eb p\u00ebr krijimin e projekteve t\u00eb reja n\u00eb Rust, por \u00ebsht\u00eb kund\u00ebr p\u00ebrzierjes s\u00eb Rust n\u00eb bazat e m\u00ebdha t\u00eb kodit n\u00eb C, pasi kjo p\u00ebrzierje ndikon shum\u00eb n\u00eb leht\u00ebsin\u00eb e mir\u00ebmbajtjes s\u00eb kernelit si nj\u00eb projekt t\u00eb integruar. <\/p>\n
Thelbi i problemeve t\u00eb mir\u00ebmbajtjes \u00ebsht\u00eb se blloqet Rust vun\u00eb mir\u00ebmbajt\u00ebsit n\u00eb var\u00ebsi nga kodi n\u00eb gjuh\u00ebn Rust. N\u00eb pamje t\u00eb par\u00eb, duket se blloqet jan\u00eb thjesht shtresa mbi strukturat dhe funksionet C, t\u00eb cilat nuk ndikojn\u00eb fare n\u00eb zhvillimin dhe mir\u00ebmbajtjen e kodit n\u00eb C. Por kjo nuk \u00ebsht\u00eb e v\u00ebrtet\u00eb. Me pranin\u00eb e k\u00ebtyre blloqeve, zhvilluesit e n\u00ebn-sistemeve t\u00eb shkruara n\u00eb C duhet t\u00eb marrin parasysh ndikimin e ndryshimeve t\u00eb tyre n\u00eb vazhdim\u00ebsin\u00eb e funksionimit t\u00eb blloqeve. \u00c7do ndryshim n\u00eb strukturat e dh\u00ebnave ose funksionet e brendshme n\u00eb C mund t\u00eb sjell\u00eb nevoj\u00ebn p\u00ebr ndryshimin e kodit t\u00eb blloqeve, prandaj ndryshimet n\u00eb kodin C q\u00eb ndikojn\u00eb n\u00eb blloqe duhet t\u00eb monitorohen dhe t\u00eb sinkronizohen me kodin n\u00eb Rust. Shum\u00eb mir\u00ebmbajt\u00ebs nuk jan\u00eb t\u00eb gatsh\u00ebm t\u00eb marrin p\u00ebrsip\u00ebr p\u00ebrgjegj\u00ebsin\u00eb shtes\u00eb p\u00ebr zgjidhjen e problemeve q\u00eb ndodhin n\u00eb kodin n\u00eb Rust, dhe nuk kan\u00eb nd\u00ebrmend t\u00eb kalojn\u00eb koh\u00ebn e tyre n\u00eb monitorimin e statusit t\u00eb blloqeve Rust. <\/p>\n
Situata e komplikuar e mir\u00ebmbajtjes nuk \u00ebsht\u00eb nj\u00eb teorike. N\u00eb diskutim u p\u00ebrfshi Jason Gunthorpe, mbajt\u00ebsi i TPM, VFIO dhe Infiniband nga NVIDIA, i cili solli shembullin e refuzimit t\u00eb Linus Torvalds t\u00eb nj\u00eb k\u00ebrkese pull me ndryshime n\u00eb n\u00ebn-sistemin e menaxhimit t\u00eb memories, pasi ky ndryshim shkaktonte d\u00ebshtimin n\u00eb p\u00ebrpjekjen p\u00ebr t\u00eb nd\u00ebrtuar kernelin me mb\u00ebshtetje p\u00ebr Rust. D\u00ebshtimi ndodhi sepse mir\u00ebmbajt\u00ebsit e kodit n\u00eb Rust nuk pat\u00ebn b\u00ebr\u00eb ndryshimet e nevojshme n\u00eb gjeneratorin e blloqeve (bindgen). K\u00ebshtu, ata q\u00eb mir\u00ebmbanin n\u00ebn-sistemin e menaxhimit t\u00eb memories gjat\u00eb avancimit t\u00eb ndryshimit, t\u00ebr\u00ebsisht korrekt nga pik\u00ebpamja e kodit C dhe kernelit n\u00eb t\u00ebr\u00ebsi, u vun\u00eb n\u00eb var\u00ebsi nga kodi dyt\u00ebsor opsional n\u00eb kernel, p\u00ebr t\u00eb cilin ishin p\u00ebrgjegj\u00ebs njer\u00ebz t\u00eb tjer\u00eb. <\/p>\n
Refuzimi p\u00ebr t\u00eb pranuar kodin e paketimit mbi thirrjet DMA e ka l\u00ebn\u00eb zhvilluesit e projektit Rust p\u00ebr Linux n\u00eb nj\u00eb gjendje t\u00eb v\u00ebshtir\u00eb, pasi pa k\u00ebto paketime zhvillimi i driver\u00ebve t\u00eb plota n\u00eb gjuh\u00ebn Rust do t\u00eb jet\u00eb i v\u00ebshtir\u00eb. Hector Martin, mbajt\u00ebsi i kodit p\u00ebr mb\u00ebshtetje t\u00eb \u00e7ipave ARM t\u00eb Apple dhe lideri i projektit Ashai Linux, si nj\u00eb zgjidhje t\u00eb konfliktit sugjeroi t\u00eb arrij\u00eb pranimin e paketimit direkt p\u00ebrmes Linus Torvalds, duke kaluar mbi mbik\u00ebqyr\u00ebsin e n\u00ebn-sistemit DMA. N\u00ebse Linusi pranon k\u00ebt\u00eb shkelje t\u00eb subordinat\u00ebs dhe praktik\u00ebs s\u00eb vendosur, kjo mund t\u00eb \u00e7oj\u00eb n\u00eb nj\u00eb kriz\u00eb menaxhimi t\u00eb zhvillimit t\u00eb kernelit, dhe n\u00ebse refuzon - do t\u00eb ndaloj\u00eb p\u00ebrparimin e Rust n\u00eb kernel. <\/p>\n
Si nj\u00eb alternativ\u00eb, Hector p\u00ebrmendi angazhimin e Kristofit p\u00ebr shkeljen e kodit t\u00eb sjelljes p\u00ebr shkak t\u00eb nj\u00eb komenti n\u00eb t\u00eb cilin Kristof e krahasoi Rust me nj\u00eb tumor kancerogjen. P\u00ebr m\u00eb tep\u00ebr, Hector shkroi se ishte lodhur nga t\u00eb gjitha procedurat burokratike, nuk ishte i gatsh\u00ebm t\u00eb besonte thjesht proceset ekzistuese dhe aludoi p\u00ebr angazhimin e rrjeteve sociale. Dave Airlie, mbajt\u00ebsi i n\u00ebn-sistemit DRM, k\u00ebshilloi t\u00eb mos e teprojn\u00eb konfliktin dhe t\u00eb kuptojn\u00eb se sjellja toksike \u00ebsht\u00eb e papranueshme nga t\u00eb dyja pal\u00ebt, pavar\u00ebsisht n\u00ebse an\u00ebtari i diskutimit \u00ebsht\u00eb i drejt\u00eb apo jo. <\/p>\n
N\u00eb diskutim u p\u00ebrfshi Linus Torvalds, i cili theksoi se problemi ndoshta q\u00ebndron te Hectori dhe vet\u00ebbesimi i tij se di\u00e7ka m\u00eb mir\u00eb se t\u00eb tjer\u00ebt, e jo n\u00eb procesin aktual t\u00eb zhvillimit t\u00eb kernelit, i cili funksionon. Procesi i zhvillimit t\u00eb kernelit ka problemet e tij, por kjo \u00ebsht\u00eb nj\u00eb realitet jet\u00ebsor - n\u00eb jet\u00eb nuk ka asgj\u00eb t\u00eb p\u00ebrsosur. P\u00ebrpjekjet p\u00ebr ndjekje p\u00ebrmes rrjeteve sociale jan\u00eb ato q\u00eb i heqin d\u00ebshir\u00ebn Linusit p\u00ebr t\u00eb pasur ndonj\u00eb lidhje me qasjen e Hectorit. Vlera p\u00ebr Linus-in ka diskutimet teknike dhe patch-et, jo ndikimi p\u00ebrmes rrjeteve sociale. <\/p>\n