Nowadays mobile is everything. In the lunchtime I saw many people are playing games. Which game? PUBG writes. And your 4GB internet are left in one day. Before the GEO, we save our internet 1GB one month. Our 4GB internet is not enough for one day. We are all internet addicts. So in the festival, before internet we are celebrating different way. We meet together, get the prize and all the other ways. Nowadays we just post on Facebook, Twitter and nowadays What do you do? Just give it in the status. No one is at home, no one is at home. Nothing is possible. No one is at home. I am not at home. Just post it. Happy Diwali, Happy New Year and save the status. Nowadays we can't live without internet. So our expectation is higher, more than higher. So what is next? How can our expectation will fulfill? How can we get more internet products? So solution is one, the IoT. So what is the IoT? Next, I will explain you major factor in the session. First one is introduction IoT, WordPress and IoT and building IoT products. So many people are getting idea about the build their own product and sponsor will get idea about the WordPress IoT products. So I will discuss all the things in the session. So first of all I would like to one question. Who is the first developer in the world? Anyone can know the name? The first developer in the world. I was born in 1989. He is built in 8040. So okay, let me simple. He is her or him? Yes, the world first developer is female and her name is Ada. So we are proud of him. So next, what is IoT? Next, what is the internet of things? If you connect anything with the internet, it will become IoT. Simple and sober. I would like to IoT example. If you have a hotel, 5 star hotel, so the waiter come to us and speak. Hello sir, how can I help you? Which food do you like? 5 star hotel. But you went a small hotel and some bhojanalai. So if you don't want to wait, you have to wait. If you don't want to wait, you have to wait. But if you build IoT products and you get more service to the client, so let me think IoT products. First of all, we build a table, IoT table. Customer will sit and get all the men on the table. And just he would pick up your order. And after the selecting order, he will get a pricing, which time get a food and all about the related order. He will get everything. In that product, he can give money on the table. He gets anything from the table. He doesn't need anything. He gets the time. I have ordered 3 rotis, it will come in 2 minutes. From there, the customer will select the food. And the payment can be done on the table. So this is an example of the... IoT products of the table. Next. Nowadays, IoT products are built more and more and more. You can see the Internet of Things in 2020. 5 billion, 0 billion products are coming into picture in 2020. Next. So here is example of IoT products. The T-shirt. The Polo has built IoT T-shirt. The biometric information you get after viewing the teacher. T-shirt, sorry. Sorry. T-shirt. Your body checkup and all the things. And you will get all the reports from the... Just wearing a T-shirt. The next one is the tennis board. You can get ball speed, board spin, and all the other related to tennis. You can get a report after you are playing the tennis match. Then property like IoT lamp. Now we have to install 4 bulbs at home. Look at green here. Some are yellow, some are blue, some are green. We all want bulbs but we can't get them in one month. So if you want to make an IoT bulb, you can use the colour bulb. Next is the farming. We can see the air, the temperature of the weather, and the farmer will know when to do it. Next. It is a benefit of IoT based on time. We will discuss on the later. Benefit of IoT, you can save time, you get more information, accurate information, you save the money and you will get quality and better life with IoT product. Next. Riggs involvement IoT. Before buying any IoT product, there are many risks that we should not see. If we build an IoT product, we will have to see all these risks. For example, cyber security. All these devices connect with the internet, so we need to see cyber security. That is a big risk. Next. Privacy issue. Privacy issue is that we can connect any product with the internet. For example, our mobile is connected with someone, someone else's Wi-Fi can be connected through. So it is necessary to see our privacy. Next. Next. Time. So now time to come a build IoT product in WordPress. So how can we make a smart WordPress? Anyone can knows the IoT WordPress product? Anyone can? Any IoT products in WordPress? Have you think we can build IoT product in WordPress? IoT scope is large, but in WordPress scope is limited. Have you knows? Today you knows. Because I provide you some examples, live example with IoT product, with the help of WordPress. Next. Use cases of the IoT in WordPress. So how can we make IoT products in WordPress? For example, we can make push notifications, we can connect with plugins, we can make a device, we can make a alarm, if our site is hacked, the alarm will ring in the morning, that your site is hacked. So you will immediately know. So this is a good IoT products. And I thought IoT products scoreboard, if you make a scoreboard of Hukomus site, then it is good. For example, if we look at crickets, then what we see? Scoreboard. Searching how many have been made, washing how many have been made. We do not see the full image, we get to know in the scoreboard, what is the spirit of the match. Similarly, if there is any product of WordPress or any site of Hukomus, then we can see the whole side of the WordPress site together. Next. Smart WordPress in real life. As I said, many products are already built with WordPress in IoT. So who is the product? We will show the Google Glass. I think all knows with the Google Glass. Who is no Google Glass? No one can? Yes. So already built IoT products with WordPress in Google Glass, I share the video link. What kind of feature in this Google Glass I will share you. Just you have to connect your Google Glass with your website and just click them. Then photo automatically upload on your website. You can also upload a video with the Google Glass directly on your site. No need to any admin connection. No need to any gradients are required for posting a video on your gallery. Next. This is already built in WordPress.org and you can get a nice huge product and MQWT. This is already a free plugin in our WordPress. Next. Integrating in WordPress. How can we build our product and how can we connect our product to the WordPress? It is only possible with the WordPress to build IoT product with REST API and JSON API. It is a bridge from connection device to the WordPress. We can build WordPress IoT product with three different platforms. One is if TT means you provide a free to you developing platform, you have to just read their algorithm and connect to your WordPress website. You can directly post your things on the WordPress site. Next is a little bit. Next. A little bit also one of the platform you can connect your WordPress website with this and you can connect your electric device with this platform. Like example, you have a singer and you want to build a rhythm and directly rhythm post to your website. This platform will provide. Next. The little bit is also WordPress plugin you can find in WordPress.org. Next. Third and important platform is Particles. Particles provide you full fill IoT products with the WordPress. Any kind of product you can build with practicals and they provide your own SDK. Next. There are the links you can learn all the build IoT products with this link. Next. Thank you for listening me.


Underneath this head cover is quite possibly my favorite ever club released by Mizuno and that's a really bold statement when you consider some of my favorite irons ever were from Mizuno and even with just half a dozen shots in I am already thinking this could be very well a go-to club in the bag for me and many others because the new lineup of fairway woods from Mizuno is something very very special and they've entered into a space that they've not been in before now obviously they've released fairway woods so what makes this lineup so different and unique for Mizuno and that shot there is exactly why it might well end up in my bag super tight fairway so much trouble on the right hand side I've got a fairway wood that zips the ball off the tee with very little effort so how's it doing that well I can report we're in the middle of the fairway well go and play an iron very surely but for now I said what makes it so special well this is an all titanium model titanium body titanium face there's 80 grams of weight that is also placed in this sole plate and then an extra eight gram that you see placed very much front and center which makes it a super low spin model in theory it's also aimed at faster swing speeds in theory so maybe it's not for me so what I don't understand with all that aimed at that better player how come I'm getting so much out of it now one thing I need to happen is an appeal to manufacturers in stop categorizing clubs based on sort of swing speed because otherwise I wouldn't go near this it's very well known that I do not swing the club fast so based on the marketing and the press release that I've received from a Zuno this club shouldn't be anywhere near my bag but trust me it plays so so well I love everything this does but what is it that I like so much about it well one of the things is the fact that it's just absolutely like a bullet off the club face what you'll see is a very penetrating ball flight from each of the shots you've seen so far and that's largely due to the way this thing is weighted because interestingly enough I've got a five wood in my hand and in terms of ball flight you don't ever guess that just lead a tad out to the right but you'll see the idea that again you can also get a super high ball flight if you wish and the other interesting bit for me is that I said it was a five wood it's also available in three but this option for me as I always say on the channel is it's super versatile lots of playability from that kind of lie from the tee and maybe even from the roof but there's also adjustability which is key and we've got sort of four degrees worth of difference that we can change this and make it fit within our bag get up ball as you can see we came up a little bit short but it gave me a great excuse to try one of the new T24 wedges from Mazzuno because right now what they're releasing is really really interesting and really elevating Mazzuno in my opinion in the product stakes and don't miss out our video on these T24 wedges because they're just as interesting as this fairway wood to be honest with you so today's video comes to you in association with our travel partner Glencore Golf and this week they sent us off to Portugal arrived in Lisbon Airport and then a short drive to Dolce Campo Real the donnell steel design golf course weaves its way through valleys mountains and vineyards and is a true test of golf in the most tranquil of surroundings breathtaking views from elevated tees and fairways that wind through our landscape arriving at well protected greens each shot requires your full attention a club also waits for post round drinks then relax into the modern hotel rooms bars and restaurants refreshed and ready to do it all again for more information on this or any other golf trip you may be planning speak to the team at GlencoreGolf.com you see just behind the club face itself there's this little was a piece of stainless steel it's encased in some TPU it's the core tech chamber the Mazzuno called the sort of missing piece in a previous model release they've kept it into these and what it does it also shifts weight forward as well all sort of pushing towards that low spin model it's very effective but what it also does is this model and previous of what they've been doing of late sounds fantastic off the club face as well they've got it absolutely spot on I mean we always spoke about nothing sounds like a Mazzuno iron but right now in their sort of driver and fairway models they've got it in my opinion really really good and then from a looks perspective they've gone down a sort of classic stylish route now I always talk about matte finish on crowns right now that being very popular for me having said all that this is just so classical in its design it looks fantastic the sort of the the size the profile it's very much a little bit of a throwback in my opinion to a traditional fairway wood and then the face has just got these white score lines either side of the centre which frame the ball really well and then from a shelf appeal perspective I just think they've got it so so good hard to pick fault with this right now in terms of what Mazzuno are doing and they've just added to their line up with it always all about the association was all about Mazzuno irons but I think what they're doing right now putters wedges fairway woods drivers they've really upped their game in my opinion oh my word that is so good I just hope the audio is picked up I'm just seeing how long that's gone well that is bang in the middle of it in fact it's still bounding on that low spin model especially from kind of this elevated position just flies on but with me with a five wooden hand I do it the ball quite high so there's always that tendency to get a sort of floaty one and that's why I said it's really interesting for me in a bag personally is because that low spin model just gives me that more penetrating ball flight but I'd say right now I'm actually swinging the club head really easy out on the golf course so it really goes against the grain in terms of that kind of what it's aimed at in terms of your swing speed so don't be put off by that sort of the direction in which this thing is pointed at in terms of type of player because like I said it wouldn't be for me but I've got a feeling this will definitely go in my golf bag right now I love it I love the versatility option it provides I love it to five what I love 18 degrees a loft that's maybe performing for me more like a forward in terms of ball flight couldn't be give more praise to be honest with you to this product love it in every single department and it would certainly take all the boxes in terms of from this average golfer right as ever thank you for watching I hope you enjoyed that one let me know what you think because I've got to admit I'm kind of always Mizuno irons yeah 100% when they release this kind of thing I'm never I'm always a little bit I don't know cautious in some ways and not I shouldn't be because what they're producing like I said is so so good right now but I'd really like to know your opinions as well are you going to give this a go but for me stg titanium fairway would from Mizuno absolutely fantastic thanks for watching I'll see you all soon


Wow! Garner to invest $21 billion into Railway. Railways have always been a driving force in the industrialization and economic growth of a country. Railways contribute to both social enthusiasm and commercial competitiveness by transporting millions of people and goods to cities and towns worldwide. The Railway has been a critical tool in driving economic growth in countries that have established transportation infrastructure. Countries such as the United Kingdom, Germany, India, Japan, China and others have seen significant improvements in their people's lives and economic development as a result of the effective use of railways as a major mode of transportation. In the 1950s, train transportation was regarded as one of the best on the African continent. The Railway was an important mode of transportation, connecting the major cities of the countries. Railway travel was extremely efficient, dependable, cost-effective and safe. The most important aspect was how it improved the local economy of traders and agricultural product transportation from the source to market hubs. Historically, Garner's railway system was limited to the plains south of the barrier range of mountains north of Kumasi. However, the 1067 mm narrow-goage railway, which spans 1,300 km, is undergoing major rehabilitation with inroads into the interior now underway. In Garner, the majority of the lines are single-tracked, with an estimated 32 km of double-tracking in 1997. Soon after independence, Garner built a massive railway infrastructure connecting the country's coastal industrial towns to the country's resource-producing areas. The economy of the country's mining, forestry and cocoa growing regions benefited from railway transit. In the 1950s and 1960s, railways were the most popular mode of transportation for Garner's small businesses and women. Due to years of neglect by successive previous governments, many Ganean have never considered using the railway system as an alternative mode of transportation. Despite the government's efforts to fill the transportation market with buses, as provided by previous administrations, the transportation system was primarily owned by the private sector, filling a gap in our deficient transportation system. Garner's initial operational rail line of 947 km in 1960, two lines. The western line and the eastern line has been reduced to 160 km in 2020 due to neglect and underfunding over the years. Garner had the highest decline in the effectiveness of available rail lines, 16.9% in 2020. Experienced a significant decrease in freight volumes transported and accessibility to railway services, 0.6% in 2020, indicating the sector's dire state. The western rail line connects Takaradi Port to Kumasi, with a branch line connecting Dunkwa to Wasa. It is 339 km long in total. Today, it is arguably the line that lends itself best to a Bouti or Burut financing model, while the eastern line connects Akra to Kumasi, with a branch line connecting Akra to Temma. Railways have recently gained prominence in the development of emerging countries, particularly in Africa and particularly in Garner. Ethiopia's colonial-era railway has also opened, thanks to $3.4 billion in Chinese bank funding. New railway systems upping built in Kenya, Senegal, Tunisia and Morocco, which are revolutionizing people's lives and national economies. Garner's rail system has been in disarray for a long time. As the governments drive to industrialize, the country continues and new mineral deposits are exploited. The prospects for investing in a modernized railway system appear promising. The sector is being restructured in order to increase private sector participation in the delivery of rail transport services in order to stimulate the country's socio-economic development. Garner has started building mega railways to all of the country's major cities and strategic mineral resource sites. The project is being funded with government resources. A build and operate transportation remit with private partners and a Chinese development bank credit facility. So far, the Ghanian government has awarded contracts totaling $9 billion to various firms in order to meet its goal of constructing 1,400 kilometers of new railway lines by the end of 2020. Other contracts for other sections of the rail network are currently being negotiated, with completion expected within the next 10 years. China Gezilba Group, China Harbour Engineering and China Road and Bridge were reported to be interested in the scheme last year, as were African Rail of Garner and the US registered PFNC Railmark. Because the government of Garner cannot fund the project with its own resources, we retained PricewaterhouseCooper as our transaction advisor and tenders were sent to the international community for interested bidders, Mr. Lombo explained. Following that, 45 people were shortlisted, which was later reduced to six. We had to be cautious with the selection process because some of the bidders were simply time-wosters. It's been a slow grind, but it's been a deliberate and responsible grind. Once Garner's railway system is completed, transportation of goods and services in Garner will be quick and easy, as will movement of people. Garner will not only develop quickly, but it will also grow rapidly. Please share, comment on and like the video if you enjoyed it, and subscribe to Africa Reloaded for more exciting videos.


So with all the fancy introductions out of the way welcome back to the podcast Matt Reynolds and Anne-Marie Mohan Matt welcome Thanks for having me and Marie. Welcome. It's a pleasure to be here. Pleasure's always mine today We're here by the talk about bio plastics and bio plastics first of all As I say it out loud sounds like a what an oxymoron oxymoron bio plastic anyway They were going to be the sober bullet that was going to solve every problem They were going to be the film they were going to be the resin They were going to be things that we were going to use that was going to be renewable and everybody was excited about it Whether it was 10 15 years ago, and I feel like everyone started throwing there aren't the budgets and things at it So I guess to start before we really get into it. Why was that the case? Well one thing that really captured Everyone's attention about bio plastics is that they're made from a renewable resource versus being made from petroleum So they use sugarcane. They use corn and now they're even using more cellulose feedstock like Wood chips and things like that. So it's made from a renewable resource And not only are they a renewable resource, but because they are they sequester carbon So they take carbon in rather than emitting it. So that's another advantage and As we moved along in the development of bio plastics There came technology called drop-in plastics or bio plastics where they have the same functionality and Same properties as a petroleum based plastic. So with the early PLA or poly Lactic acid which was the biggest thing to happen like back in 2000 or so The problem was that you could make the bottle. It didn't have the same properties It was really sensitive to heat and then it also would contaminate the recycling stream But for a consumer you couldn't really tell the difference in bottles. So they'd just throw it in with recycling But with drop-in bio plastics, you have the same functionality They can be recycled and so that was a huge advancement in the technology interesting so that the good Plastics would contaminate the bad plastics essentially bad being my turn for in the recycling team, but this stuff from natural resources I guess because it's not the same Interesting. I wouldn't have thought of it that way. I guess I just figured it would fizzle out once it got to the Recycling functionally. It's the same but you know as soon as it gets to to the mirf then that's where trouble occurs Right the mirfs. There's a lot of trouble at the mirf and we've understood that as we've done a series of these podcasts All right, so this stuff is awesome. Why isn't it everywhere? Why are we not seeing it on every shelf? Why isn't it? Well, I mean one thing that's changed since you mentioned 2000 to the early 2000s is Um, you know plastics in general have just really taken a perception beating You know So the focus on sustainability as it pertains to packaging is now You know the eye is cast on plastics and bioplastics are still plastics They're still they're still there's still a kind of an alphabet soup of p e p e t all these kinds of You know letters that confuse consumers and and scare consumers because they're not exactly sure how to recycle it And as emory said some of them can't be recycled. I think early on there was this misconception that You know because the bios in the word they assume they're biodegradable right so over the years We had to be real careful about defining what biodegradable is just because it's bioplastic doesn't make it biodegradable necessarily And the differences between compostability and backyard versus, you know industrial compostability and biodegradability. These are all very kind of Venn diagrams that overlap a little bit, but you know, they're not the same thing So it's further confusing to the consumer. It costs more bioplastics costs more. I mean, that's a Always the driver. Yeah. So petroleum based virgin plastic is really high quality and it's super cheap the way it's It's made right now and there's a lot of efforts right now to kind of level that playing field and create some you know, uh, you know Make make sure that the the finances or the economics isn't the only driver there, you know, and there's some worry about You know food is a worry if if if bioplastics are coming from corn and from You know sugarcane, you know Is that eating into the world's food supply now, you know, that's a that's a it's a genuine concern I think since then we've realized that the percentage is really really tiny That's actually eating into what potentially could be food and now as and re said now you're starting to add cellulose non food cellulose food waste or Or non food, which is wood chips or food waste as you know second, you know post post use food especially I mean imagine like Brewers giving up their you know spent barley or something like that So so so that's not as much of a concern But it was just one of many that kind of pumped the brakes on what we thought in 2002 or something like that would be This silver bullet And yeah eating up r&d budget very slowly over the course of time is what's happened instead of it being some big You know immediate threshold moment. Yeah Okay, so we So I guess we use this last these last, you know decade or whatever to Well, we didn't we didn't have to spend the r&d unfortunately But now that they've kind of ironed this all out and learned all this Are there some examples now that we have out there in the marketplace that Are finding ways to apply this? absolutely and one of the Biggest suppliers of bioplastics That i'm aware of where we've really seen a lot of applications both in region and in flexible is Braskham And they do a drop in bioplastics. They do drop in polyethylene and We have several examples of what they're doing originally They were supplying part of the feedstock for Coca-Cola's plant bottle They also worked with the company in the uk To make a reusable bottle. So it was for tourists there who would get a water bottle and then Just litter so there's a lot of litter from tourists and now you can get the bottle filled and then reuse it. It's a very durable Recyclable and reusable package So delicious almond milk is used for their packaging There's a toothpaste tube from Ireland that's using The Braskham drop in bioplastics. So yes, we definitely have applications now You say that That coca-Cola was using braskham. Are they not still I remember and I remember you just Obviously saying 30 seconds ago, but I also remember reading this they were using them and and now it seems like here Are you implying that they're not anymore? Well, what's really exciting is just recently they were able to come up with or or crack the code on engineering a completely Bioplastic bottle plant-based bottle. So formerly they were using 30 bioplastic and I don't know It's been maybe 12 years that they've been developing this lot of r&d And they switched and I I don't know exactly why they made the switch or You know, they were looking for suppliers. They were investing in different companies But now they're using 30 hardwood from forestry and sawmill sidestreams And then 70 percent is now from corn and sugarcane, but it is not braskhams It's a different technology that they're using And then at the same time some Tory beverages also just announced that they have completed a 100 percent plant-based bottle now in their case They're using 30 percent material from molasses Which is very interesting and they were doing that before and then 70 percent is from non-food feedstock So they were They both kind of hit the finish line at the same time, but it's very exciting Yeah, that is now for for Coca-Cola, for example, are they I Will admit I don't drink a lot of soda. Is this just I know I've seen with like the disani and stuff like that Are they able to use this across their product line? Or is this something that's something like a water? Like I mean Just the different beverages have a different effect in the bottle or can they use their whole product line in these bottles? My understanding is that they could use it across the bottles Right now they're waiting for a commercial scale up of this technology But their goal really isn't to replace what they have now. It's to be another option So they're trying to reach all these sustainability goals. And if I you know look at my notes here They've said that their strategy is to use 70 percent to 80 percent recycled PET and then use We advance recycling and renewable materials for the other 30 percent. So they're not Moving to plant-based, but it's an addition to Okay, another tool in the toolkit. Yeah, I was gonna say so it's another way to meet a certain number or a certain goal And I understand that Okay, so are there I guess the What I'm thinking is are there other kinds of bioplastics besides these I guess what we've been calling drop-ins Things that you know that can go with PE or PET being used at the marketplace Yeah, there's a lot being done with uh, you know starches thermoplastics or excuse me. Uh, yeah thermoplastic starches I just covered one. Uh, I think it was a year ago now though It was with sealed air and it was a pasta company out of seattle called kuchina fresca Hopefully i'm pronouncing pronouncing that correctly. I feel like I've had that before. Yes possibly Yeah, I mean they sell it out of like that pike place market or whatever. So But they the litting material it was a thermoplastic tray with pasta inside and I don't remember if it was nap It could have been nap of modified atmosphere, but uh, it was a matter of the litting material turning to this thermoplastic starch That was an interesting and it wasn't the full amount. It was a percentage of it using it But then on the subject of starches, there's also, you know, a lot's being done with potatoes potatoes starch And there's a few different versions One of them's water potato that uses resonance It's a biologic with the the logic with a q from new plastic plastic with a q Sorry, I had to look at my notes for that now There's a reason and that's yeah 20 to 30 percent of the of the pack itself The pouch is is from that tps or a potato based starch so and then also Alexia potatoes from land Watson are using a potato based starch in the pouch So the interesting thing there is you've got potatoes in In the pack and the pouch is made from potatoes in a sense or at least a portion of it So there's some some circularity there. I was going to say that's yeah that that's that that seems very circular Um having potatoes and potatoes So I guess are there to kind of Put a button on this discussion bioplastic So there are others out there that we haven't touched on because so far Like I had no idea about the potatoes I didn't know about the wood and the cellulose So I'm learning at least somebody out there is definitely learning along with me So there are other ones out there that would be noteworthy that we should get out I mentioned that the one of the early misconceptions is that all bio bioplastics were You know biodegradable by nature and they're not but as Anne Marie knows that at least one or two of them are So I think one of them was yes, there's a really exciting new technology that Has been in development for quite a few years And uh, it's called pha the resin is called pha and I can't tell you I know what it stands for but I can't say highly hydro alkanoid Um, and it's made from a naturally occurring organism, which is One step beyond what we've been seeing and what's really noteworthy about it is that it is marine biodegradable um one company that's been working with Danimer scientific, which is one of the biggest companies that i'm aware of that's working on this technology is Frito light And they just released a compostable package made from this pha material The product is off the eaten path. So Some people may remember that years ago PepsiCo was really ahead of its time in creating compostable Snack bags But the problem at the time was that it was too loud So they fixed that And uh, so this is a very exciting development So that yeah, they did get the sound out of sunships people were very unhappy that they're Potato chip that or their sun chip bag. Excuse me. It was too loud, which in and of itself is hilarious because Priorities, right? Yeah priorities and chip bags are exactly silent as anyone who's ever been in a movie theater would know And bachardi is also using this technology too. Yeah, so it's big between frito lay and bachardi Those are two big brands. Yeah Fantastic And I I guess to kind of wrap up and again I thank amory and matt for your time is that one thing that you've said a lot And I don't know that I've really highlighted or we've highlighted enough is marine biodegradable from what I understand by saying That is that that's something that In the end will not harm the ocean, correct? That's my understanding of it. I mean that's and that's the biggest thing with classics That's the biggest thing that we're we've always hearing is that at the end of the day. Yes We would we see it in landfills and stuff like that, but then you see these pictures of these massive You know Plotilla, thank you of plastic out in the ocean so that marine biodegradable is a huge thing that I know came up often and it's really exciting so that we won't Hopefully continue to harm the oceans in the future so that that would no longer be a drawback So again, thank you amory. Thank you matt for joining us and go out there and get some bio plastics


Hi guys So talk about what I've been up to lately as you probably noticed there are there are get trees now in kernel.org I like to talk about what I'm doing about that and what I plan to do in the future I'd subdivide my tree into three major categories That's hot fixes that stuff's going to go into Linus in this RC window Memory management, which is going to go in the next merge window and then non-MM Which is another? Concept which will go also in the next merge window and that includes a OCFS 2 and I a 64 which I am the maintainer and Proc FS and you name it everything else hundreds and hundreds and hundreds of subsystems Which I have taken patches in the past will take patches in the future most of them empty at any point in time and Of course, I'll mainly be concentrating on the larger part, which is the MM part All three of these things hot fixes MM and non-MM. I divide into two bits one is the stable bit, which is a non-rebasing get branch based on MM's master branch, which I'll cut around that RC 2 RC 3 With a plan to leave it there until the next RC 2 or RC 3 so it goes back and edges are naughty on top of the Stable material, which is a non-basing tree for Linus in the next merge window I'll have the unstable tree, which will be sorry. It's a quilt queue and That will be rebuilt on demand As I do releases All of this material MM hot fixes unstable MM unstable non-MM stable unstable all rolled into a master branch called MM dash everything and that goes off to Stephen Frank inclusion in Linux next and I'll probably recut all these branches two three times a week to keep everything nice and updated in Linux next I Like to keep things that in a quilt tree because it is so flexible Well, things are churning and being stabilized and getting ready to go into the The under the into the stable branch I Can and will if prevailed upon do so do direct get pulls From your branches, but I don't think it works. I don't think I've ever seen a substantial patch set which got through unscathed a Couple of years ago 15 20% of the mm patches I had for dash fixes. They're real functional code changes and Then they're all the changes to the changelogs, which turned at a tremendous rate So my preferred approach is to stabilize stabilize stabilize we decide okay This patch set is now ready to go into stable MM dash stable and I'll talk a bit more in a few minutes about What I'd like to do around that process Once we decide it goes into stable I want to take the quilt patches a crunch mill together fold in the fixes to a final pass across the changelogs Then merge them into a branch under mm stable and that's hopefully where things sit Now of course shit happens. I might eventually have to take a branch out and put it back and unstable or throw it away all together We can do that Alternatively if the originator of the patches with the author really really wants me to Pull their get tree well, I can I'm going to have to handle myself across to them Make sure it comes back to me as identical to what I already have and I will check that That's the easy part, but I'm also going to one check all the changelogs are what I had as well I carry far less dash fixed patches patches than I used to Mainly because I've got lazy if you send me if I'm on v4 and you send me v5 I used to go through it and go all the little v5 fixes so we could see what you changed Now that I just check out v4 silently and re-merge v5 so I've less dash fixed patches, but the code is still churning and Don't know it doesn't matter if you I've seen it if you're a version 11 You're a version 16.  I Mean poor old gear how many times we've broken the m68k we always break m68k Yes, I would prefer to keep things in called tree if prevailed upon to do so Yeah, I can send it back to you and you send it back to me But it's latency in its work and things can get lost And incidentally when I do drop your v4 series and merge your v5 series I'll stick kill keep on my little dash fixed patches patches against v4 Just to check whether you incorporated everything and sometimes. Oh, it still applies The submitter missed it missed out on some fixes, which I had so I can double check that branching structure What I have a present for this cycle is really lame The nm unstable print is just a guilt acquit a quill queue every patches Parenthood office predecessor I'll say sorry to Linus and try and get it and merge the whole lot of one hit But then for the next merger window. I want I want to do is go for a very flat structure What? Everything every patch series ideally is based off master and they all get merged and here patch series could be a single patch I'm I think I'm looking at having a separate branch for every single individual patch because if the scripting is right That should be cheap implications of being Probably best if you were to target the mm master branch Which would be cut off RC2 or RC3 because we're gonna remain there But really I don't care because I'm gonna quantify things, you know You can work on last Linus main release. You can work off RC2 Like a nest mainline you can work a flindex next. I'll figure it out based on anything you like really whatever's most convenient But don't base it on Windows NT. That would be a problem Branch naming so I expect after the next merge window have many many many branches these branches will have long names If a patch series is in the unstable queue it'll be mm dash unstable dash And the rest will come from your zero of n email. So you get to choose the name of the branch I'm wanting to ask as I move on to the idea of topic branches is that within the subject of your patch set Which may be a single patch? Please identify what subs what topic you believe it belongs to You know if I've patches that I'm trying one one hell what topic is this it could be a memcg patch Which changes three lines of mem control that see in 30 lines of VM scan dot see so by line count It's a VM scan patch, but in fact functionally it's a memcg patch So please I'm gonna ask the originator to decide what topic you think this is and that will be reflected in the file No in the name of the branch and The reason I want to do that is we can look at the branch name and directly relate that back to the subject of the Email on the manual list. We can go both directions, which I think it's pretty neat if we get the naming right I'll do a large and boring Document and once this is all settled. I'll get that in the documentation directory Which say if people do it wrong I can politely point them at this this section 45 a please This is the process. Please do that I Hate changing the subject on your emails because then that we no longer Can relate what I've got to what's on the manual list. They can't relate that to name of the patch So I think getting the subject right and appropriate is gonna help ease the process along So I'm okay. You can choose whatever branch you you is best suits your needs. I'm gonna attempt to base Your patch queue on on the master branch Sometimes I may have to branch it off one of my existing branches That's okay. I'll make sure my tooling handles that and The branch structure of these many branches will all be captured in my good old series file So my cook you was also in colonel at all in a separate get tree. There'll be a stable link to the series file Which will describe the branch structure in some manner which I will describe and That that'll be a stable URL and I update that several times a day when I'm working I think the only if I've got a particular branch sitting in the AM stable queue Let's say it does something to VM scan My preference would be not to base your work on that but base your work on RC three unless you are really explicitly logically working on somebody else's code which is in this Kernel cycle and that's very rare It's very rare for somebody to work on somebody else's patch set that hasn't gone into a linus yet on The occasions where it does happen. It's the same person, you know, they don't want to patch series and another patch series Which which bases off that? So it's fairly rare so a flat tree structure should work unless the amount of conflicts becomes totally unreasonable Topic branches, you know, other subsystems use topic branches They don't make a lot of sense to me if I've got the patch against VM scan that does one thing or another patch against VM Scan that does another thing that unrelated each is its own topic The only relation between is they happen to hit on the same file and maybe textual conflicts So I will have topic branches But I think really the only reason to have one is so I can reasonably chunk stuff up to send into linus rather than just Enormous, please pull the whole world Now that's bad in a way because for Linus pulls of VM scan Topic and then doesn't pull MCG for another couple of days then we're sitting there in an untested state He's got code which we've never run before not on Linux next to run anywhere before But this has been happening forever. I don't send the entire quilt queue to Linus and one here I'll send them a hundred then another hundred and then seven and then we're done There is a risk that will introduce a bug in one patch and then accidentally fix it another one I think it's only ever happened once so there's a risk and I'll dialogue it with him I think the risk is pretty low So yeah, I ask you people to choose the name of the patches and to allocate the subsystem it goes to That's all patch wrangling shit. There's some people shit on top of this It's all very nice to have a stable non rebasing good tree against which to do ongoing development But that's only useful if we've got something in it Last weekend we're at RC for and I went through all my various patch passing. Okay. What can I move in the stable branch? Series after series after series was not ready a little little cross marks You know, I'm waiting for the reviewer to come back. I'm waiting for the submitter to respond to review I'm waiting this test results to come in. I'm waiting for this person I think should review it to show some sign is actually read it. We got bugs everything RC for halfway through the RC cycle was not yet ready to go into the stable tree So if we want this process to work, I mean, I think we should be more Expeditious about getting these patch sets nailed down. Just don't let things dangle on weeks after week after week and So I will become more active about this and I will help I'll send little emails and they're almost always gonna be private emails I don't want to put people on the spot and embarrass them. I'm just gonna ask you Can you please respond to this one? I want you to understand where I'm coming from and just trying to hurry things along Yes, maybe Just just a question. So one of the things that you Have been doing is to merge changes to your tree as soon as possible and One thing that I and that might be really great in many cases But one deficiency that I have found in that process is that this leads to a lot of fix fix fix fixes and also a unclear situation for the submitter because Whenever you see your patch being merged into your tree You are almost half done So attention to that work decreases considerably right and that's probably the reason why you have those Waiting for somebody. So my question is Would that be a process regression if patches get really merged After they they are not having any Comments like I'm waiting for somebody or something to happen I reread the email you sent me a couple years ago on this topic and yeah, it sounded that's what you said sound awfully familiar I do actually skip version one a lot more than I used to I Don't do it visibly. I'll send a little note person say thanks I think I'll skip version one or I'll let this person look at it or The trees full right now. I just Keep the originator particularly if it's a new person. Just let them know where we're at what my thinking is Please resend it. I'm gonna wait for viewers to provide input So I don't always aggressive leap on version one and sorry to a large extent. It depends who it comes from So if a person thinks that my merge means okay my work here is done that was an inexperienced person I Do like provide guidance to those people to help them understand where things are coming from So that sort of happens under the hood I Always welcome people assembly private email, you know, just send me an email saying I don't think you should merge this yet Or I want to look at it or I don't trust this. Just let me know what you're thinking. I'll take that on board Is that cover? So in general, I mean, I like your style of doing things that that appeals to me and it's been working out great for me Sometimes I feel like we should push more for review before pulling a series into Next for example because like lately we've seen lately. We've been seeing quite a lot of Breakages in next and the patches the question were not reviewed yet So I was wondering what we can do about that because obviously like lately There are a lot of code changes and we have like limited review capacity For example, I try to review a lot, but like the last couple of months. I was busy working on other topics that Took longer than expected. So like I'm wondering if if that should be something to focus on that Like we only pulling pulling something after People looked over it and agreed that it's like in a decent shape or if you really want to go ahead And let's say you say skip version number one I was wondering if that is like a good condition to put something in or really wait for until like Let's call the sub maintainer although that doesn't really exist like says or yeah Like we can give this a shot. This might be worthwhile to expose to next or something like that Yeah, I I don't think I want for get formal review to Be gating on merging it in next time. I'll do my best to look at it I particularly see who it comes from I bought it myself. I think this has got a good chance of going in So I like to pipeline these things To attempt to accelerate the process get them under runtime testing in next while these things are happening But have some in the notes to myself, you know, it's not going to proceed further until I think the appropriate people have looked at it and as long as submitter understands that and Again, if you do want to review this patch set me don't have time Send me a little note. No, I'm a little like mark on it and I can help with that But I think sort of overlapping the runtime testing PR bot tracker fuzz testing along side the review Let's just get these sort of review level things and the runtime things happening concurrently So and you said you kind of didn't want to call people out on hey, I'm waiting for you on this But do you think there's room for more transparency? Like I think there's just the time that in terms of like saying Showing the state of the queue and saying this patch is Especially waiting on more review like can people perceive that in your patch file or that private information for you They certainly can okay if they they know to look and they know how I work But this is why I'm becoming I want to become more activist about this You said present the decision to move a patch set from unstable to stable It's something I do very late in the place basically doing the merge window and I do under my own cognizance I want to fix both those things. I don't want to do it late anymore. I want to move it up You're RC4 RC5. Let's get it go this while I'll be poking people. Can we please get this wrapped up? Now the thing I haven't touched on yet is I don't want to make this decision on my own People are fallible not just me and I could miss an email. I could miss interpreted email, but also you people could fail By failing to make it clear to me that you still have issues so I could think everybody's cool So what I'm going to do now. I'm not just going to take a patch set and move it into the stable branch. I Want to run it by everybody else first But I'm not going to say is everybody okay if I merge it in the stable.  So what I'm going to do is I'm going to say I am going to measure this two or three days from now Nobody says anything. I'm going to put it in Okay, and you can send me a private email I feel like if you're really stressed out about this and I will figure it out, but no I want to solve these two issues of getting the end of the stable treat very late and Having to do it all by myself And I'll do that with irritating little emails Understand where I'm coming from Now I think this moving of a patch set or a patch from Unstable to stable is a big deal and so we need to concentrate around that a little bit Now When do we decide to move a patch set from unstable into stable end of the non-rebase and get tree which is often It doesn't have to be perfect When we merge it when I put it in stable tree like says at RC 5 we got many more weeks RC we've got the next merge window week all the next RC. That's three four months We've got to get it up to production quality and to be realistic We've got it probably another couple of entire kernel cycles before anybody uses this code in anger So we have many many many months to sort out the last little 1% We'll have a lot of pipe lining going on in our kernel processes Let's use that. I mean let's not throw any old shit in all this is tree Obviously, we need to be diligent and do our best Let and we're not going to know what's wrong with it and do more and more people roll it out and test it on more and more machines But no, I think the criteria for moving something in this table is Does Linux want this and is it good enough? It doesn't it's gonna be is it perfect?  Thank you for CC stable. That's wonderful So when I asked, you know, I'm moving this I plan to move this into stable in a few days time Please ask yourself do I really think Linux wants this feature and do I think it will be production quality? Is this documented anywhere two three months from now? Because actually I was asked I went around before coming here I went to everyone in my department saying what would you like me to bring and one of the topics came out I think it was exactly what you just said could we document the criteria of getting stuff into mm? That was actually almost verbatim what was asked to like you know have something that we could say this is what we You know if we look at this and we could say hey we pass this it would likely Move forward or whatnot or maybe we could fix it or whatnot Maybe there are some things that shouldn't be written down But that would have probably solved a lot of issues over probably wait and save wasted time and such to know like you know Having an idea of like should we go with this features or something we could pull it? How do we go about getting it in getting accepted having something documented or something where we could you know? So people don't waste their time doing a lot of work and then finding out no no one wants this or no, you know go away Well, I do still will be the case right? It still will be the case people doing a lot of work and then finding out nobody wants it. Yeah Yeah, but having some idea about like you know documented Criteria that says you know at least there's a 90% chance or 80% chance that you might actually get it I don't know well I will move all this stuff in a documentation file put in the documentation directory, but the words around that thing I just said will be guided You know we really shouldn't be putting stuff in the tree until it's perfect. Well, sorry This is the real world. How many express that and formal document and don't know I Have a more general question now once we have the MM tree Do we want to create sub-bierarchy likes the networking guys do or drivers guys do or we continue to have separate reset for my Mem block for wheelies a page cache and so on Okay, so do we want to merge everything in the end into the MAM tree or we continue to keep separate tree for separate MM Subsystems well mem block is sort of its own little world world. I've never ever had a conflict with your mem block tree I don't have many patches, right? So I get a nasty email from I mean if you want to Get me to pull on the mem block tree I can do so or you can just send it the linus independently as Flush to me it does with slap. I'll continue to send to Linus independent. Whatever works, but largely question like Probably will create more conflict or will be a base for for different work on top of it So does it make sense to merge really stream to a mem tree? Which tree will is tree? I wish we lived stop writing patches Okay, I found the on switch I Also wish I would stop writing patches So, you know, obviously folios have been hugely disruptive from all points of view I think it's gone quite well considering It could have gone so much worse. I've been really pleasantly surprised with how Few bugs there have been I was expecting this to be far harder than it has been But I think I I think I'm almost done with the hugely conflicting changes between MM and FS and this and that and the other I think things are going to Settle down at least for a little bit I think a large part of the problem we've been having is that you weren't using a git tree before now and I so the the future MM patches that I have indeed the MM patches I have for this cycle I'm sending to you. I'm not planning on having On on doing a git pull to Linus for MM folio patches Now for file system folio patches, I am going to be doing a git pull for Linus Most of the people in this room will not have seen those patches because you're not subscribed to the next FS Debell And that's fine. You don't need to be that's, you know, you're not process and developers and There are going to be and there are some some conflicts and I've marked them as such and Stephen Bothwell has run into them and he's followed the instructions in the patches that says just drop this patch because there's a Conflicting change over in Andrew's tree. It's the swap B page stuff that was Definitely needed and I'm so happy has gone in I wish had gone in you know years ago, but Time So yeah, I think I think That I will continue to run a git tree But it won't contain very many patches which conflict with memory management because I'm going to be funneling most my memory management changes through Andrew through through what you The final bullet point right for myself is okay, we have this nice non rebasing MM stable tree What uses it We don't really want people to base work off it. I prefer the base of master so everything's flat and I could merge it and thank God for git re re re So I don't really Anticipate that many people will do they work off it if you're someone like Willie He's got some super patch that bashes up bashes that the bashes on everything Then he'd rather he'd be better off looking for conflicts with the MM unstable tree Which is everything which plans to go on the verge window But It's there. We'll figure it out as we go along Yeah, Mel go ahead I Very strongly suggest against Defining criteria for why a patch that could be merged because once any criteria is actually specified. It's something I'm a gamer fight Yeah, okay It's Once you lay down guys is these are the rules people try game fight was roots and it's something that Shows up to some extent Well too much less recents in schedule or land in CPU schedule land where people try and like gamify what the criteria are and get like Slap down repeatedly over and over again and I don't think that is is Really something that you should do but in terms of the the rebasing versus non-rebasing thing and when things are considered stable or not stable Let us this criteria for Allowing Tree or a get pulled to be pulled in is based on has this thing been tested or not So if there is an RC to a Stable tree and then there are stuff that needs to be ripped out and it needs to be Redone against a later RC then so be it at least in in mm in memory management It's relatively rare for patches to conflict with each other directly in schedule or land There can be subtle interdependencies between different series that go in so the tend to layer stuff on top of each other Are these say it should be done against at the latest sketch tip that should be done at any given time But that that problem rarely happens at least in my experience in mm most of The series are actually independent of each other and if it comes to the case that We need to rip out something in RC 4 and RC 5 and the baseline moves That's fine as long as there isn't a rebase and RC 8 or an RC 9 Where the accepted patches get reassembled so like stuff coming in and out is It's just not that severe of a problem if it needs to be pulled out and we need to and the mm stable It gets rebased at RC 4 or RC 5. I don't think that should be considered a major problem Just sort of do that. I'm not as new to basis Exactly and like it would be kind of like a flag day Then it says, okay, the base is somebody was working off mm stable and there's a major disruption in RC 4 well then too bad The figures will have to be whatever figures that you use to justify that your series go in or just have to be redone And we would hope to be relatively rare But at least my primary working workflow right now is that I do everything against RC 1 And I do piles of individual series some of them are mm based some of them are scheduler based as according as each one Individually passes testing. I assembled them to make sure that they all work in combination Which is particularly important to schedule or less important than mm But like if something needs to get thrown out it gets thrown out So just make sure that they end result is still okay, and that's fine up until you're at least at RC 5 once our RC 5 I Find there's pretty much no point trying to send a new series at all. I might so just wait through the next merge window well Well, it depends how big a change it is from one to the next but I Think for an individual developer If you want to do runtime testing RC 2 could be a bit flaky I think the best approach there would be for you to just locally merge up with Linux's latest RC 6 and do your testing Right, you do your runtime testing on the result of that merge Even though your patch that remains based on RC 2 and of course Steven is going to do that as well He's going to integrate I change it with the latest reading edge linus kernel and we'll get the runtime testing results back from that One final note our little head. I always had there. There is one little tree which Is special I will be maintaining often I get these patches which are kernel-wide, you know somebody renames everything or does some stupid shit or or it take it a It explicitly works on patches which are pending in Linux next or something So I will have a little cue which will probably always be a guilt get a quilt queue of Kernel-wide patches and then I'll sort of independently feed that through the back door to Steven for inclusion in Linux next and Send it to Linus probably as a quilt patch bomb very late in the merger window But I would be very reluctant to significant mm material in that series Basically mm stuff should be based on RC 2 not Linux next But that include Like file system interactions like or you're talking about like things that are actually kernel-wide like What what trips what trips it into that? workflow is when Because the only damn thing I can get the patch to apply to a make any sense is Linux next I was essentially I wish the point one nothing's working. Yes, so I'm going to move the patch to behind Linux makes some magic It applies. That's the main criteria. So as long as it functionally makes sense and Syntactically applies. Yeah, I'm going to cure it up behind Linux next It's very much a moving target and I wait things to stabilize at the end of merge window before presenting it to Linus That's what I got Yeah, so I would like to get back to the I think that Mike has brought up and That's about sub-maintainers because we currently have few areas that are handled by a git tree and For some reason I I still cannot cope really well with with people bypassing you and sending pull requests to Linus directly because to me it seems like a Potential problem long-term what by completely balkanizing the whole mm and not having a coherent picture of of the area and Do you think that it would make sense to Have growing number of sub-maintainers so that you do not have to care yourself about those areas and Made essentially pulling from them as they ask you so you get those nice Let's say pull requests with the description descriptions of what the changes are so that you can when you are sending your pull requests, you do not have to care about those high-level descriptions and If you are okay with that what would be the Where that work would be Gathered like it would be the stable branch where you essentially when you are getting a pull request from a sub-maintainer You just merged that into this stable branch and then once you are done with the current let's say Merge blend and you send a pull request from that branch or how do you envision that thing? Yeah, that would work I wouldn't want to put in stable branch until it is stable until you know We agree that this is hopefully unchanging from now until that until the merge window So it initially put it in the unstable branch because it's unstable And then as that we see the appropriate manner of view come in Then at some point in time will agree to move it into into the non rebasing stable trick Okay That sounds like a great improvement to me I'm speaking for myself, but I Guess that this would make the process much more transparent also for others and That would be cool. Yeah, I still want to see that said the appropriate manner of view from the appropriate people have enough runtime in the next max and And I'd still like to say, you know, I Think it's time to move Michelle's branch from unstable Distable I'm going to do that three days from now If I don't see any objections. I'm doing it. I still go through the same process. Yeah. Yeah, sure I mean that there will be likely a lot of things to be sent through patches not through the gateway, but we seem to have some areas that are maintaining their sub little thing and Yeah, that was my primary concern that Just to grow that sense of Sub-maintainers that might even encourage more people to be actively maintaining their areas Because you would be pulling from them like as we see in other Other areas. Yeah, I'd still like them to follow the same Diligence, you know all those little reviewed buys of those little act buyers Adam make sure all the appropriate people CC that the change like additions come in that Every little fix is rolled in and doesn't get dropped on the floor somehow Even if you're not delegating the actual Code movement like what it makes sense to declare Somewhere like the review team because I know when I I know when I added a new memory zone Dave Hansen got a got a ping from Andrew saying Dan or a few people like you're kind of in your in the MM inner circle like got notified like hey, is this okay? Should we back this out? Are people aware that they're maybe maybe they already know that they're kind of in that reviewer team but it kind of works from the Like how the x86 mm side works with anything there. We there's like Andy Peter Dave We they you talk you talk to them before it goes to the tip tree So they're not actually they're not actually sending code to tip, but they're they're the gate can not my gatekeepers But they're like the review team that kind of a well the maintainers fire can capture that Accurately enough. I don't think there is any sort of formal Siloization there. I don't think it's appropriate because so many people to say busy and doing stuff And so it basically I end up making judgment call and where things would be adequately reviewed It might be by a regular person or a part-timer But I don't think having hard and fast Go no go team would be workable And to some extent, you know people may end up reviewing it post facto and we've still got those months to fix it up And also backtracking in a long way I'll talk about the readiness of a tree to become stable When you we need to agree that it's But it's a desirable feature for Linux and that it's it's ready enough Cleanups cleanups are wonderful. We will have cleanups, but cleanups can be deferred indefinitely I don't think cleaning up the code Should be a gating issue if you think move this function here rename this to that and that sort of thing Yeah, fine. It's desirable, but we can do that them next RC As long as the codes got at runtime, you know cleanups can be deferred So I don't think that should block inclusion migration of a patch set into the stable branch I Just had a question. I thought I before today I thought I had a rough understanding of where to base my patch sets, you know At any given time, you know right now, maybe you say okay today RC one is out So I know I should base my patch set on RC one or or but now I've lost that confidence and as I wondering if maybe you could just kind of run down and say, okay You know, here's the situation where you would base it on RC one Here's the situation where you'd base it on Linux next. Here's one where you'd go for MM stable Well, my preference would be of Of MM gets master branch. I mean I could draw a line in the sign Sam and say I'll cut RC to So that RC to will be my target from merging these things but you can work against linus is most recent at least probably and Things will be fine. So to large extent. It's whatever is most convenient for you What makes most sense for you Probably not Linux next that's that's a stretch Yeah, so we have lost him along the chat and he he's saying that I think for pool from a sub maintainers The reviews would be already gathered by them and the pool would go directly to stable at that point of time or at least that that's his understanding so So yeah treating it as any other patches patch set or any other patches Wouldn't really save much work for you That's fair enough as long as that I'd like to see that patch set and we're talking about the slab series here Has already been in Linux next for a long time. So I assume that's being independently included by Steven So even before he's got all the reviews coming and hopefully if this stuff is already been rounding in Linux next for a week or two So yeah Yeah, the slot trees also continuously being exposed to Linux next the question would be if if to also do this Exposure through your tree or independently or and only the The end result would be Going through the mm stable tree, I guess we can Look at how other Trees with sub maintainers do that Could but main slabs pretty damn standalone. I think what we've been doing for the past few months has worked. Okay I've never observed any conflict between my get a nasty email from Steven So I think just keep doing what we're doing and just treat it as an independent branch. I Just send it directly to Steven to Linus. I don't think I would add any value Okay, it works for me, but The question was if there was more Sub maintainer sub trees like for example, mcg or whether that should Really break the mm3 To pieces that would be independent or or whether we should strive to unify them in the end I've gone quite no There are a lot of peripheral stuff in mm. I mean memory hot plug slab Z three-fold zs Muller go that stuff, which is pretty standalone But the core material mcg vm scan page a lot and map huge tlb It's just all Everything's smeared together. I think decoupling those amongst maintainers amongst trees will be It'll be a nightmare Few years back when I was trying to mimic your free with with get free I essentially was doing that by topic branches and then merge things together And I was quite surprised that Conflicts about those different areas for example my mcg or hot plug were really been minimal So do you think it would make sense to at least try that approach or? Maybe I'd like to try this approach for a few months and see how it goes, but I Mean if it makes sense if it'll give us something better than what we have yeah, why not? Okay, because I believe that we can sit with with Roman and Neoness and create a mcg part for that that would be probably one of those larger source of patches in your tree and Yeah for memory hot plug I believe that David and Oscar are doing quite a lot of work right there. So maybe they can't come up with something and Yeah, if you're willing to try that approach then yeah But worse can happen then we just throw everything away and and just apply those patches, but you know Well, let's let me get this get this stabilized and go through a couple of cycles with it and then start looking at moving that stuff in Mcg does have a sticky little pause a lot of places that my worries me a bit So what what I wanted to bring up in a context was something that was raised upstream that Especially people that are new to the kernel or to mm. They sometimes don't have a clue who to cc And I mean if you do get maintainers on a specific file, you're mostly out of luck I mean get you and then like 200 people that committed court sometime Yeah, so the question was then whether we actually want to define for example in maintainers some MM subsystems and not necessarily at maintainer attacks, but for example review attacks and I was actually proposing to do that soon for example for memory hot plug Like just the most important files that I care about and then I might just get like see see it more often So to say I was wondering if that should be then something we should discuss in general I mean, I'll propose a patch to do that, but maybe it makes sense for other subsystems as well Yeah, fine. I think get I think get maintainer and the maintainers tree handles up pretty well the files You're interested in you put your name in there and you'll get even more email Yeah Yeah, but then I don't have to dig through Linux amendment like find out that there is something interesting after three weeks when catching up Part of part of my life is making sure the right people were CC Just a small note like I think adding Documentation files and test files into maintainers file actually raises awareness of just like people don't know that they exist And like adding it makes it more obvious I don't think I follow that sorry I'm saying that like just listing Test tests like which exists like self for example memc group castle tests or like as a any any sort of testing and Also, like any sort of documentation in the maintainers file It's a good thing just to kind of raise an awareness that they exist Right. Yeah. Yeah. Yeah for see groups. I added like Castle of test like recently and I think we should do this more often Okay Mill talk to us Gonna be heard you can you hear me? Fright, sir. Oh Okay I'll take that would be me classic I exist in the maintainer file With an R entry under scheduler and it's far like just one specific config parameter for anything schedule or releases where if something is coming in that's Is affecting that config that I meant to review is it's not some possible to have the same for Breeding management. Now, we don't have the same granularity Are the same breakdown both we can document in the maintainers file that someone is not necessarily a sub maintainer But if you are touching a particular part of the memory management that you Should at least get an act from this person are some acknowledgments that they've at least seen it So different a part of my role to make sure the right people have looked at it and rubbed in their nose So you all have a lot of maple tree reviewing to Can't argue with the logic We don't know I get to sit down yet. Oh good No, okay, so When when when you send maybe a larger patch set sometimes you have to set certain things up before you actually get to the meat of what you're doing and I'm just wondering how the message in That beautiful pretty cover letter Will get merged in in the new plan How's it handled in the Upstreaming Well, you know, I tend to put it inside the first patch and I think I will continue to do that Okay It means it means that like the maple tree for instance. I'm setting up Test framework at first so that you're gonna have like all this information about how the maple tree is gonna be you know making sliced bread For the first time versus and and and it's gonna be in the patch that says like add print error to The radix tree Test infrastructure, so it's just wondering if that could be handled in a different way. Yeah, I mean that that's Yeah, it's a bit silly to do that, but you can just have the one-liner seat patch five the details Okay well that had to link back to the morning list but Mm-hmm You'll have the info in Well in this in my patch one I have a link to the zero of N as well as the link to this particular patch I always do that so go to link to the head of series as well So yeah, people will figure it out but to your But then should your first patch be a documentation patch back to the mic request and Because a lot of times there's like really good details in the change log like why is it's not in documentation? It's like a good narrative well, well I usually the I Put that with the whole the the data structure, right? So the code goes in and the documentation and then the next patch was a huge test patch So I mean I guess I could put The big patch first and then the setup for the test that comes next Or It's just kind of it's just kind of Other other places in the kernel they have this the merge right and then that goes in The get pull or whatever, right? So you have the the one that actually has no code, but it's just like a huge Documentation on what what's going on in the next 50 patch 70 maybe who knows I Guess I've seen when you've pulled in the change log You'd like Andrew tends to pull it into the passion makes the most sense and like oh, I'm glad you save my save my cover letter because I Would have forgot what this does. Yeah Yeah Okay, I think leaving the merge request kind of leaves it stranded Yeah, I might get lost in history. That's true, right? Unless you dig through the get log for specific information, but usually most of it Hopefully is in in the code slash documentation, right? I mean apparently I'm the only one who does that but but other people are going to start today, right?


The following is a production of New Mexico State University. Gardeners all over the Southwest are selecting more and more xeric plants to create unique and water-wise landscapes. Today we're back in the Colorado Springs Xeriscape Demonstration Garden where Valerie Club Conservation Specialist will introduce us to a variety of beautiful xeric plants. Some will be more appropriate for high mountain areas and some for low-lying desert areas. The Missouri gardeners here in the Southwest have to realize how diverse, how varied and extreme this gardening climate is. We range from high mountain plants down to low desert plants. You've got a pretty good collection here. We do. We've got a lot that will go even higher up than what we are right now, such as the caragana, the pea shrub, which has a beautiful yellow bloom on it. The bur oak is a very sturdy tree. We've got the three-leaf sumac, which is a wonderful shrub. It comes down pretty far into lower elevations, too. Yes, it does. It's a wonderful fall color. And then we've got, as we come down the slope here, we see some of the wildflowers that we might see in the Southwest, penstemons, the grasses. Yes, we've tried to incorporate a lot of different ornamental grasses because of their value in the winter. And Artemisia with one form of the sagebrush. Yes, the blue color is wonderful. And as we come further down, we see some ground cover plants. The soap ward of the saponaria. This is really our ground cover demonstration area. We've got the soft landing time, which has been a wonderful time. And a couple of different kinds of Veronica that give us a lot of color. And really striking show of penstemon in here. We also have, I don't know if you noticed, the dwarf rabbit brush, which is a little two-foot-tall one. So it's really appropriate for this area. And as you go further down into the low desert, rubber rabbit brush is one of the common plants. In fact, it's sometimes called chemisa. As we come down out of the mountains, then we leave the ponderosa forest behind, and the spruce are far above that. And we come into the pineon forest, the pineons and junipers. And the big western sage, you can see. And the lower Artemis is here. And don't forget the choyas. They're very popular, even as high up as we are. And when they bloom, they're beautiful. But when you step on them, they hurt. Yuccas, another one you want to watch. Yuccas, yes. They're beautiful. They've bloomed a lot this year. They ran down into the rubber rabbit brush? Yes, lots of rabbit brush. This is really a wonderful thing that we have in our garden. In terms of the whole garden gold in the fall, doesn't it? Beautiful. Just beautiful.  You've got some representatives of that here as well. The low desert is the realm of the cacti. You'll see some yucca and other things as well. But that's really where we think of the cacti. Absolutely. But we don't want to confuse the cactus and the rocks with zero scape. Right. This is still zero scape. Yes, it is. If you had only cactus and rocks, you might have a true zero scape. Yes. But if you bring the native plants in, add to them some adapted plants. Absolutely. Some design and put together the principles of zero scape. You've got a zero scape. And the lowest water using zero scape. Yes. The lowest water-wise. Which is very pretty. With the little soft peach colored flowers. Yes. The patchy plume is a beautiful plant all four seasons. Both of these are natives. Absolutely. And some ornamental grasses. The blue ravina is very pretty. You've got the woods rose. Which is in the forest that comes down. Small elevations with very little water. And does very well wherever it goes. And then some non-native but adapted plants you can use. The lilac. The hawthorns. The mack oranges. Mack oranges are beautiful. They're in bloom right now. And you've got the amorphous. The false indigos. So there's so many things you can bring in and design it properly. You'll have a landscape that looks good, uses relatively little water. But it's easy to take care of. True zero scape, yes. And if people want to know more about that, this is open. Absolutely. We're open all the time. If you want some of our paperwork, we're open from 8 to 5 during the week. We're always open. It's beautiful. It's sunset and dawn. And every time in between. And you've got a website. We do. It's csu.org. Valerie, thanks for showing us around. You're very welcome. It was my pleasure.


Yeah, that is you know, really the plan of action and this this by the way, this this pullback on the dollar I'm expecting it to be quite deep Yeah, I am expecting it to be quite a deep one Depending on obviously the currency pair, you know It could be you know hundreds of hundreds of pips because we've had a massive, you know trend on that dollar So I would expect equally expect a very deep pullback Yeah, that could last and that narrative could last for a third for several months, but Ultimately if You know the data supports the narrative that you know, these guys are heading into a deep recession Yeah, sooner than the US Then it's a case of just timing your dollar entries because then it will be the dollar will be a potential buy at some point Yeah so Planning out the next, you know, six months. This this is that this is this is my plan of action And so yeah, any questions on that? Oh, by the way, sorry It was a Alexander says correct me if I'm wrong didn't power mention that they did not want to repeat of the mistakes of what they did in the 80s So can you be more specific? So what happened in the 80s that he's referring to in terms of they don't want to repeat of that If you can turn on your mic if you want Alexander. Yeah, I just did I'm in the 80s from What I read on research that they hike and from hiking cycle They went back to cutting and then because they noticed the mistake that went back to hiking again, okay So this was this was a mistake that they did not want to repeat But my main question is asking about this because the reason it's exactly from what you mentioned and you say a dollar pulled back And it is obvious that the dollar is is gained strength not because as we can see the results of easy that the dollar the year US is not is still a strong currency or strong country More in demand compared to other countries around around the globe absolutely Why like why okay? I can understand the pullback because but for why that long like what why would you say six months like? I really want to get around this Like you say six months or a deep pullback because we had a really bad Wouldn't this be more looked at as a technical term or as a fundamental term like which what logic? Do we say that you might pull back to six months? I would say I thought about I don't know if I said six months Maybe three to yes, maybe three to six months Who knows and the only reason why I'm putting that timeline in timeline in timeline in sorry Let me get the words out Is to kind of manage your expectations of what the pullback may look like right now These things do take time in times of remember fundamentally You know, we're looking at medium to long longer term time horizon So the reason why I would say a pullback of maybe, you know, three months to six months Is because there could potentially be The narrative that you know, once the Fed start to you know trail off and the ECB is still hiking the The Bank of England is still hiking is that remember the data tends to lag So we don't get you know the first quarter data until The second quarter we don't get the fourth quarter data into the first quarter So when I say three to six months it may take Three months or six months in that in actuality to confirm You know that Europe or the US or say US or as a matter of fact all three of Of these countries are actually in a recession, right? So let me just explain that again so it could take members to negative quarters to confirm a Recession and so If you know two quarters is three months or a quarter three months two quarters is six months, so the narrative Yeah, I'm expecting the narrative and I'm not trying to forecast it But I'm just trying to adjust my expectations and your expectations that if you start to see a deep pullback come A pullback could last for months Yeah on on the dollar, right? So when I say three to six month on the throwing it out there, but also from the perspective of Just adjusting our our timeline in terms of how long we may want to you know, short the dollar For example could be one month, right? And these things can change. We have to be dynamic I'm not saying this today, you know, and that's gonna be it set in stone Of course things change automatically But I'm preparing for these things and if I start to see the evidence show that these things are occurring Then I've already mapped out the plan Yeah, rather than trying to react to these things that may or may not happen So when I use, you know, six months six months is probably more of the extreme end Alexandra so from that from that perspective, maybe it might be a bit far out But at the end of the day, I'm prepared for a dollar pulled back to last for that long because how many times have we seen? You know Price just continue to fall or continue going higher and everybody's watching their heads and saying oh Well, you know the dollar should have turned round by now But you're maybe two weeks or three weeks into, you know a certain cycle where you know Remember that all the banks want to buy the dollar or they want to sell the dollar for example And these things can take months to play out So that's the reason why I have that timeline doesn't mean it's going to happen But I have the six month time now I may be more on the extreme end But maybe probably three months you might get, you know, two to three months You may get a dollar pullback. That's just, you know, that's just the reason why I'm explaining That time and how would that make sense? Yeah, kind of makes sense, but things basically fundamentally so basically if there's any dollar pullback would be mainly due to over expensive US dollar because it's rich where it's rich, but fundamentally we've also Seeing that the dollar is in that position because it's It's like we said the dog with the least feelings or at least compared to to Euro great Britain if any country which Um Does have a strong economic right now, but even though they're the first I'm starting to cut rate not sorry to hold rates It'll be Australia, but Australia Also being a commodity one of the strongest commodity currencies is being affected because of its risk of environment so like basically, so it'll be more more of a And a pullback due to a dollar being expensive. So this this this will be one one one of the main reasons Do you believe? So are we are we shifting to Aussie dollar now because I was I was no no just in general in general like I'm just So so comparing the two but like like the dollar like for a fundamental reason for adults to have a pullback Either one month or three months in the environment that we are we Surrounding right now because we're in a strong risk of environment Yes, things may shift things slowly slowly look like if they may shift But this is a mate with a question But leaving that on the side looking at the at the at what's what's being presented to us and like Like I still believe the dollars are very strong by but yeah, so what reasons what reasons like fundamental Will be for the pullback. That's that's that's what I'm trying to find like and that's what I explained because of the of the dovish pivot Right. I just I was I was just saying I know I did kind of deleted it But I was saying because of the dovish pivot. Yeah, the dovish pivot what we typically know about fundamental analysis Is that the central bank that it tends to hike rates? Yeah Should be the one that you should buy and the one that is not hiking rates Yeah, is the one that you should sell look what happened with the australian dollar recently, right? They started to dovish pivot and look what's happened to australian dollar Yeah, obviously alongside the fact that we are in a risk of environment But the australian dollar once they you know adjusted expectations the market has to now re Value what that interest rate hike or the the lack of interest rate hike the value of the australian dollar versus other currencies Hence the reason why you've been seeing You know the euro was he for example, you know start to go higher, right? We're talking about this Right, the reason why didn't take that trade and I and I said to you know, I said I'm not taking it Yeah, I'm not taking the australian dollar. The reason why is because of the dovish pivot, right? So there's there's there's a lag that comes in. Yes, I understand that the the australian dollar is economically better than european Best likely to to to um to weather the storm in terms of you know recession, etc But these things take time to play out within the market. There's there's Positions have to be unwound positions have to be built and this is not positions from just one institution This is from hundreds of you know thousands of institutions all small big, etc, right? And liquidity has to be created as well. These things take time these can take months for these things to to to to to play out, right? So the point the point I'm trying to make is this all right.  Yeah, but From the perspective of dollar strength. Yeah You can't expect and if you go, you know back through, you know, all the data From from years decades for example, right? Whenever you get, you know Large moves and I guess maybe look at this from a maybe a weekly perspective, right? It gives a better perspective when you get a large move like this without there being much of a pullback. Yeah Eventually you will get a deep pullback You will get a deep pullback and you know, if you look at for example certain forecasts forecasts will generally, um, you know over the long term are predicting that the um You know the dollar should want to pull back, right? So maybe one to you know Three months you should start to see maybe some sort of you know, one elevens But then you start to see prices pull back might be six or twelve months again Not to say that this is exactly what's going to happen, but You can see pullbacks occur, right? Where the dollar has to be Revalued because the dollar is less likely to go or I want to say let's like to go higher But if they start to hold rates, yeah, it doesn't mean that you know the dollar's gonna or how I place just because You know one country is hiking rates over another doesn't mean that Always mean that we're going to get you know a you should buy this currency over this currency because At the end of the day, as I said, it all depends on the economic standing of that currency and that and that country So I think there will be a revaluation of the dollar once We start to the fed start to Come to the end of their hiking cycle first and as that starts to happen With the bank of england and the and and the ecp still hiking rates There's going to be some sort of you know residual effects from that Yeah, wild banks start to adjust right and grab liquidity, etc And that could result in you know, our a slow pullback could result in a sharp pullback Nobody knows but if you take this low to this high, yeah You're going to get a pullback. You're going to get a decent sized pullback. Yeah, and so because we haven't had one for what since if you're looking at what may 2021 Right, we have not had we're gonna look if you're looking at this technically now I don't really like to be driven technically but One of the things that I know is that whenever you get a trend at some point you have to come back to fair value Right, so we know this to be an absolute low Yeah, and so let's Do the fifth tool right and so what we want to what we want to look for is a pullbacks to To fair value. Yeah, so just imagine that we're doing this right At some point prices will always pull back to fair value always pull back to fair value Whether it's a ranging fair value or an auction fair value, which is what we do here Or whether it's a moving fair value or the moving average fair value They will always come back to a fair value, right? So we've just seen this strong move here. Yeah, and there's been no pullback to 50% Remember just and just keep in mind. This is a weekly chart as well Yeah, so there's been no pullback and as we go higher Yeah, as we go higher fair value obviously moves because this becomes this is still a bargain price But this becomes, you know, either expensive or it's not right depending on whether prices go higher or lower but this You're 50% of this low to whatever the high is Is the fair value that you're looking for on a decent pullback So anyone who hasn't you know got involved in this is now looking for a pullback. Yeah So at least a fair value. So let's go forward. Yeah, so let's go forward and I'll just speed this up a bit Right Actually, let me do The read time speed Right, so it still hasn't pulled back. We're gonna move this up to here now. Yeah So it hasn't pulled back to the 50% yet. We've made new highs There that's the new high still hasn't pulled back to fair value. Yeah start going higher Still hasn't pulled back to fair value So this is the new high down to the low Still hasn't pulled back to fair value hasn't done a decent pullback yet And it hasn't and it won't and this is a weekly chart, right? Right to where we are. So it makes sense It makes sense for me technically and fundamentally Yeah for price to for the dollar to want to pull back to at least Somewhere around the fair value because we haven't done so for You know over a year May 2021 And we're heading to 2023 so technical reasons why we want to have a deeper pullback But there's also fundamental reasons as to why you know, we will get a pullback Yeah, but this may be more technically driven who knows but the point being is that Is there gonna be a period where you want to get short on the dollar? Yes, but does that mean that because it comes down to here? Yeah, does that mean that oh, we're you know, it's it's a reversal on the dollar. Absolutely not It just means that the smart money who had a bigger picture Perspective, you know a high time frame perspective We're just looking at buying the dollar, right because they understand that hopefully at this point Wherever well, wherever price has come down to it might not come down to fair value, but the you know Wherever it comes down to and that represents a deep pullback At some point the narrative Is probably going to change to say all right then well, are we focused more on gdp or are you focused focus on recession because at some point The pound yeah Right the pounds Gbp And the euro are also Going to do what with their with their interest rate hikes What are they going to do with their interest hikes eventually? no They're already hiking. So what are they going to what are they eventually going to do? Hold right and if two central banks are holding Then what then what are you going to be what divergence? What metric are you going to use to Determine whether you know you want to buy um The uh a certain currency So we've already said it like pretty much a hundred times gdp, right? That's exactly it. Who's in the recession and who's not? And so that when that moment comes in the dollar pulls back and everyone has the realization now, okay Well, you know, we we've made enough money on the on the interest rate narrative Right diverges narrative now europe and in the uk Are not hiking rates now all of a sudden you've got you know europe and The and in the uk right in a deep recession But the but the u.s. Now is not in a deep recession In fact, they're looking to come out of their recession sooner or they were there in a shallower recession So then now that becomes the divergence, right? That then pushes the dollar higher This pushes the dollar down based off of dovish divergent dovish Uh, you know a hawkish pivot also a dovish pivot, right for the dollar, right? But what reevaluates the dollar then becomes the narrative change between the economies Because who wants to buy The uk or into europe or europe or european economy When you've got the u.s. And that's what this is basically saying this this is our call. We're saying who's going to be the first to to to be the um to to get themselves out of um, you know a recession Who's best place to weather the storm? i'm just walking through What i you know what i see On a price chart and preparing i guess myself and you guys As to what the trade ideas are likely to be So i'm just going to read uh ken's comment ken says i think it's also going to come earlier Then we see due to investors seeing the data earlier and the market is forward thinking and will then price That in as they see it i think as soon as we see the core inflation is starting to come down And that's when it's absolutely so and that's really the trigger You know, we were talking about this last week fed, you know the fed pivot will be triggered really by inflation It has to be triggered by inflation. So ken's absolutely right. We could see it sooner. Maybe maybe not even though