Is vnode number also limit system-wide number of open file?
I notice that there is a unsigned long i_ino; in definition of `struct inode' [1], which is the virtual filesystem inode. Does that mean "inode number" and is it used for indexing in the system-wide inode table? If that is the case, would that limit the number of open file in Linux? I know there *is* such a limit, and superusers can adjust that by /proc/sys/fs/file-max. Currently I cannot raise that to too high, otherwise the system would crash, which I think is because I have limited memory. But, the point is, if I have lots of memory in my machine (say hunderds of Gigabytes), would the number of open file system-wide limited by the `i_ino' above? Since its type is "unsigned long", I guess I can only open 2^(sizeof(unsigned long)) file simultaneously? -- Yubin [1]: http://elixir.free-electrons.com/linux/latest/source/include/linux/fs.h#L575 ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: cross compiling
Toolchin for compiler linux? ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Update a newly-created '.config' file with some predefined values
On Tue, 30 May 2017 12:28:34 +0300, Roman Storozhenko said: > Hello everybody, > > I have a host machine and I have a VM machine running CentOS 7 with 3.x. Ther e is > a kernel source tree on the host. I have made 'make menuconfig', > populated all options that I want to have in my custom kernel and as a > result got a '.config' file. Then I copied a centos-default distro config fil e from my VM's > 'boot' catalog to my host's kernel source tree catalog. So now I have > two files in my source tree: '.config' and '.config.old'. I am able to > see difference between them using the following command: > > scripts/diffconfig .config.old .config | less > > But is there anyway to update values in '.config' file with the > apropriate values from '.config.old' file? > I just want to make sure that all modules will be included in a > new custom kernel. If you want *ALL* modules, just copy the centos-default config to .config If you want everything from your custom config, copy *that* to .config If you want to mix-and-match, you're probably going to end up running diffconfig in one window, and 'make menuconfig' in another, and for each thing that's different, decide if you want it included or not. Oh, and copy the config that's closest to what you want to .config to minimize the number of changes you'll need to do. pgppe0oISE0tk.pgp Description: PGP signature ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Update a newly-created '.config' file with some predefined values
Hello everybody, I have a host machine and I have a VM machine running CentOS 7 with 3.x. There is a kernel source tree on the host. I have made 'make menuconfig', populated all options that I want to have in my custom kernel and as a result got a '.config' file. Then I copied a centos-default distro config file from my VM's 'boot' catalog to my host's kernel source tree catalog. So now I have two files in my source tree: '.config' and '.config.old'. I am able to see difference between them using the following command: scripts/diffconfig .config.old .config | less But is there anyway to update values in '.config' file with the apropriate values from '.config.old' file? I just want to make sure that all modules will be included in a new custom kernel. Thanks in advance, Roman ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
