Context Navigation

18:29 Ticket #4536 (acess JFFS2 sb->s_root) closed by Sebastian Huber: invalid: Replying to chenjin_zhong: > Replying to Sebastian Huber: > > Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: > > {{{#!c > > static void rtems_jffs2_do_lock(struct super_block *sb) > > { > > rtems_recursive_mutex_lock(&sb->s_mutex); > > } > > > > static void rtems_jffs2_do_unlock(struct super_block *sb) > > { > > rtems_recursive_mutex_unlock(&sb->s_mutex); > > } > > }}} > > Suppose that a GC thread or other thread/task calls jffs2_garbage_collect_pass, and then operates sb->s_root by jffs2_iget.meanwhile, the main task accesing sb->s_root. a global lock for each JFFS2 instance can't work. It is not a high performance approach, but it works. See testsuites/fstests/fsjffs2gc01/init.c.
18:26 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) closed by Sebastian Huber: invalid: Replying to chenjin_zhong: > Replying to Sebastian Huber: > > Yes, the f->sem is an empty structure, it is not initialized, it is not used, locked or whatever in RTEMS. This is intentional and not a bug. I repeat: The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance. > > Thank you! I got it. but we Suppose that a GC thread or other thread/task and main task calls jffs2_do_readinode simultaneous. a global lock for each JFFS2 instance can't work. It is not a high performance approach, but it works. See testsuites/fstests/fsjffs2gc01/init.c.
15:07 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) reopened by chenjin_zhong
14:53 Ticket #4536 (acess JFFS2 sb->s_root) reopened by chenjin_zhong: Replying to Sebastian Huber: > Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: > {{{#!c > static void rtems_jffs2_do_lock(struct super_block *sb) > { > rtems_recursive_mutex_lock(&sb->s_mutex); > } > > static void rtems_jffs2_do_unlock(struct super_block *sb) > { > rtems_recursive_mutex_unlock(&sb->s_mutex); > } > }}} Suppose that a GC thread or other thread/task calls jffs2_garbage_collect_pass, and then operates sb->s_root by jffs2_iget.meanwhile, the main task accesing sb->s_root. a global lock for each JFFS2 instance can't work.
14:45 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) closed by Sebastian Huber: invalid: Yes, the f->sem is an empty structure, it is not initialized, it is not used, locked or whatever in RTEMS. This is intentional and not a bug. I repeat: The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance.
14:43 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) closed by Sebastian Huber: invalid: Yes, the f->sem is an empty structure, it is not initialized, it is not used, locked or whatever in RTEMS. This is intentional and not a bug. I repeat: The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance.
14:42 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) reopened by chenjin_zhong
14:40 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) reopened by chenjin_zhong: Replying to Sebastian Huber: > Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: > {{{#!c > static void rtems_jffs2_do_lock(struct super_block *sb) > { > rtems_recursive_mutex_lock(&sb->s_mutex); > } > > static void rtems_jffs2_do_unlock(struct super_block *sb) > { > rtems_recursive_mutex_unlock(&sb->s_mutex); > } > }}} I have compared it with Linux JFFS2. The peice of source code in Linux is as follows,As shown in black-body section, the f->sem is not be initialized and locked in RTEMS. […]
05:20 Ticket #4538 (mutex is not initilaized in jffs2_read_inode) closed by Sebastian Huber: invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]
05:20 Ticket #4537 (mutex is not initilaized in jffs2_new_inode) closed by Sebastian Huber: invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]
05:19 Ticket #4536 (acess JFFS2 sb->s_root) closed by Sebastian Huber: invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]
05:19 Ticket #4535 (acess JFFS2 sb->s_root question) closed by Sebastian Huber: invalid: Thanks for your interest in the RTEMS port of JFFS2. If you have questions, then you could also ask them on the devel@… mailing list. The RTEMS port of JFFS2 does not use a file system internal locking. There is a global lock for each JFFS2 instance: […]

Note: See TracTimeline for information about the timeline view.

Download in other formats:

RSS Feed