From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com> To: Richard Weinberger <richard@nod.at>, <linux-mtd@lists.infradead.org>, <adrian.hunter@intel.com>, <dedekind1@gmail.com> Cc: <linux-fsdevel@vger.kernel.org> Subject: Re: [PATCH RESEND] ubifs: Introduce a mount option of force_atime. Date: Tue, 9 Jun 2015 10:57:31 +0800 [thread overview] Message-ID: <5576561B.20402@cn.fujitsu.com> (raw) In-Reply-To: <55761D51.7000005@nod.at> On 06/09/2015 06:55 AM, Richard Weinberger wrote: > Am 08.06.2015 um 12:07 schrieb Dongsheng Yang: >> - ubifs_assert(mutex_is_locked(&ui->ui_mutex)); >> if (!ui->dirty) { >> + if (!locked) { >> + /* >> + * It's a little tricky here, there is only one >> + * possible user of ubifs_dirty_inode did not do >> + * a budget for this inode. At the same time, this >> + * user is not holding the ui->ui_mutex. Then if >> + * we found ui->ui_mutex is not locked, we can say: >> + * we need to do a budget in ubifs_dirty_inode here. >> + */ >> + struct ubifs_budget_req req = { .dirtied_ino = 1, >> + .dirtied_ino_d = ALIGN(ui->data_len, 8) }; >> + >> + ret = ubifs_budget_space(c, &req); >> + if (ret) >> + goto out; >> + } > > So, this is the new case when ->dirty_inode() is called via generic_update_time()? > Did you research whether you can detect that case also by looking at the flags parameter? > I'd give I_DIRTY_TIME a try. This way you could get at least rid of the mutex_is_locked() > usage. Thanx Richard, yes, we can use it to check if we need a budget here. But without removing the conditional lock as you suggested in last mail, that would not help a lot. Then I think I need to try more to find a better way about this feature by looking more into the flags. :) Thanx Yang > > Thanks, > //richard > . >
WARNING: multiple messages have this Message-ID (diff)
From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com> To: Richard Weinberger <richard@nod.at>, <linux-mtd@lists.infradead.org>, <adrian.hunter@intel.com>, <dedekind1@gmail.com> Cc: linux-fsdevel@vger.kernel.org Subject: Re: [PATCH RESEND] ubifs: Introduce a mount option of force_atime. Date: Tue, 9 Jun 2015 10:57:31 +0800 [thread overview] Message-ID: <5576561B.20402@cn.fujitsu.com> (raw) In-Reply-To: <55761D51.7000005@nod.at> On 06/09/2015 06:55 AM, Richard Weinberger wrote: > Am 08.06.2015 um 12:07 schrieb Dongsheng Yang: >> - ubifs_assert(mutex_is_locked(&ui->ui_mutex)); >> if (!ui->dirty) { >> + if (!locked) { >> + /* >> + * It's a little tricky here, there is only one >> + * possible user of ubifs_dirty_inode did not do >> + * a budget for this inode. At the same time, this >> + * user is not holding the ui->ui_mutex. Then if >> + * we found ui->ui_mutex is not locked, we can say: >> + * we need to do a budget in ubifs_dirty_inode here. >> + */ >> + struct ubifs_budget_req req = { .dirtied_ino = 1, >> + .dirtied_ino_d = ALIGN(ui->data_len, 8) }; >> + >> + ret = ubifs_budget_space(c, &req); >> + if (ret) >> + goto out; >> + } > > So, this is the new case when ->dirty_inode() is called via generic_update_time()? > Did you research whether you can detect that case also by looking at the flags parameter? > I'd give I_DIRTY_TIME a try. This way you could get at least rid of the mutex_is_locked() > usage. Thanx Richard, yes, we can use it to check if we need a budget here. But without removing the conditional lock as you suggested in last mail, that would not help a lot. Then I think I need to try more to find a better way about this feature by looking more into the flags. :) Thanx Yang > > Thanks, > //richard > . >
next prev parent reply other threads:[~2015-06-09 3:02 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-08 10:07 [PATCH RESEND] ubifs: Introduce a mount option of force_atime Dongsheng Yang 2015-06-08 10:07 ` Dongsheng Yang 2015-06-08 22:35 ` Richard Weinberger 2015-06-08 22:55 ` Richard Weinberger 2015-06-09 2:57 ` Dongsheng Yang [this message] 2015-06-09 2:57 ` Dongsheng Yang 2015-06-09 3:24 ` Dongsheng Yang 2015-06-09 3:24 ` Dongsheng Yang 2015-06-09 5:00 ` Dongsheng Yang 2015-06-09 5:00 ` Dongsheng Yang 2015-06-09 5:09 ` Dongsheng Yang 2015-06-09 5:09 ` Dongsheng Yang 2015-06-09 6:36 ` Artem Bityutskiy 2015-06-09 6:36 ` Artem Bityutskiy 2015-06-09 8:02 ` Richard Weinberger 2015-06-09 8:02 ` Richard Weinberger 2015-06-10 3:16 ` Dongsheng Yang 2015-06-10 3:16 ` Dongsheng Yang 2015-06-10 9:21 ` Artem Bityutskiy 2015-06-10 9:21 ` Artem Bityutskiy 2015-06-10 10:10 ` Dongsheng Yang 2015-06-10 10:10 ` Dongsheng Yang 2015-06-10 10:25 ` Artem Bityutskiy 2015-06-10 10:25 ` Artem Bityutskiy 2015-06-10 10:34 ` Dongsheng Yang 2015-06-10 10:34 ` Dongsheng Yang 2015-06-10 11:05 ` Artem Bityutskiy 2015-06-10 11:05 ` Artem Bityutskiy 2015-06-23 9:55 ` Dongsheng Yang 2015-06-23 9:55 ` Dongsheng Yang 2015-06-23 10:44 ` Artem Bityutskiy 2015-06-23 10:44 ` Artem Bityutskiy 2015-06-23 23:49 ` Dongsheng Yang 2015-06-23 23:49 ` Dongsheng Yang 2015-06-24 0:33 ` Dave Chinner 2015-06-24 0:33 ` Dave Chinner 2015-06-24 16:04 ` Artem Bityutskiy 2015-06-24 16:04 ` Artem Bityutskiy 2015-06-25 9:55 ` Dongsheng Yang 2015-06-25 9:55 ` Dongsheng Yang 2015-06-25 10:08 ` Artem Bityutskiy 2015-06-25 10:08 ` Artem Bityutskiy 2015-06-25 10:10 ` Dongsheng Yang 2015-06-25 10:10 ` Dongsheng Yang 2015-06-25 11:28 ` Artem Bityutskiy 2015-06-25 11:28 ` Artem Bityutskiy 2015-06-26 1:17 ` Dongsheng Yang 2015-06-26 1:17 ` Dongsheng Yang 2015-06-26 7:01 ` Artem Bityutskiy 2015-06-26 7:01 ` Artem Bityutskiy 2015-06-26 7:13 ` Dongsheng Yang 2015-06-26 7:13 ` Dongsheng Yang 2015-06-26 7:43 ` Artem Bityutskiy 2015-06-26 7:43 ` Artem Bityutskiy 2015-06-26 7:52 ` Dongsheng Yang 2015-06-26 7:52 ` Dongsheng Yang 2015-06-26 8:19 ` Artem Bityutskiy 2015-06-26 8:19 ` Artem Bityutskiy 2015-06-26 8:22 ` Dongsheng Yang 2015-06-26 8:22 ` Dongsheng Yang
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=5576561B.20402@cn.fujitsu.com \ --to=yangds.fnst@cn.fujitsu.com \ --cc=adrian.hunter@intel.com \ --cc=dedekind1@gmail.com \ --cc=linux-fsdevel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=richard@nod.at \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.