From: "Huang\, Ying" <ying.huang@intel.com> To: Dave Hansen <dave.hansen@linux.intel.com> Cc: Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>, Michal Hocko <mhocko@suse.com>, Johannes Weiner <hannes@cmpxchg.org>, Shaohua Li <shli@kernel.org>, Hugh Dickins <hughd@google.com>, Minchan Kim <minchan@kernel.org>, Rik van Riel <riel@redhat.com>, Daniel Jordan <daniel.m.jordan@oracle.com>, Dan Williams <dan.j.williams@intel.com> Subject: Re: [PATCH v2 1/7] swap: Add comments to lock_cluster_or_swap_info() Date: Wed, 18 Jul 2018 11:09:25 +0800 [thread overview] Message-ID: <87bmb5gryy.fsf@yhuang-dev.intel.com> (raw) In-Reply-To: <0b478120-1af2-1251-361a-58c30b258ca3@linux.intel.com> (Dave Hansen's message of "Tue, 17 Jul 2018 11:27:27 -0700") Dave Hansen <dave.hansen@linux.intel.com> writes: > On 07/16/2018 05:55 PM, Huang, Ying wrote: >> +/* >> + * For non-HDD swap devices, the fine grained cluster lock is used to >> + * protect si->swap_map. But cluster and cluster locks isn't >> + * available for HDD, so coarse grained si->lock will be used instead >> + * for that. >> + */ >> static inline struct swap_cluster_info *lock_cluster_or_swap_info( >> struct swap_info_struct *si, >> unsigned long offset) > > This nomenclature is not consistent with the rest of the file. We call > a "non-HDD" device an "ssd" absolutely everywhere else in the file. Why > are you calling it a non-HDD here? (fwiw, HDD _barely_ hits my acronym > cache anyway). > > How about this? > > /* > * Determine the locking method in use for this device. Return > * swap_cluster_info if SSD-style cluster-based locking is in place. > */ > static inline struct swap_cluster_info *lock_cluster_or_swap_info( > struct swap_info_struct *si, > unsigned long offset) > { > struct swap_cluster_info *ci; > > /* Try to use fine-grained SSD-style locking if available: */ > ci = lock_cluster(si, offset); > > /* Otherwise, fall back to traditional, coarse locking: */ > if (!ci) > spin_lock(&si->lock); > > return ci; > } This is better than my one, will use this. Thanks! > Which reminds me? Why do we even bother having two locking models? Because si->cluster_info is NULL for non-SSD, so we cannot use cluster lock. About why not use struct swap_cluster_info for non-SSD? Per my understanding, struct swap_cluster_info is optimized for SSD. Especially it assumes seeking is cheap. So different free swap slot scanning policy is used for SSD and non-SSD. Best Regards, Huang, Ying
WARNING: multiple messages have this Message-ID (diff)
From: "Huang\, Ying" <ying.huang@intel.com> To: Dave Hansen <dave.hansen@linux.intel.com> Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Michal Hocko <mhocko@suse.com>, Johannes Weiner <hannes@cmpxchg.org>, Shaohua Li <shli@kernel.org>, Hugh Dickins <hughd@google.com>, Minchan Kim <minchan@kernel.org>, Rik van Riel <riel@redhat.com>, Daniel Jordan <daniel.m.jordan@oracle.com>, Dan Williams <dan.j.williams@intel.com> Subject: Re: [PATCH v2 1/7] swap: Add comments to lock_cluster_or_swap_info() Date: Wed, 18 Jul 2018 11:09:25 +0800 [thread overview] Message-ID: <87bmb5gryy.fsf@yhuang-dev.intel.com> (raw) In-Reply-To: <0b478120-1af2-1251-361a-58c30b258ca3@linux.intel.com> (Dave Hansen's message of "Tue, 17 Jul 2018 11:27:27 -0700") Dave Hansen <dave.hansen@linux.intel.com> writes: > On 07/16/2018 05:55 PM, Huang, Ying wrote: >> +/* >> + * For non-HDD swap devices, the fine grained cluster lock is used to >> + * protect si->swap_map. But cluster and cluster locks isn't >> + * available for HDD, so coarse grained si->lock will be used instead >> + * for that. >> + */ >> static inline struct swap_cluster_info *lock_cluster_or_swap_info( >> struct swap_info_struct *si, >> unsigned long offset) > > This nomenclature is not consistent with the rest of the file. We call > a "non-HDD" device an "ssd" absolutely everywhere else in the file. Why > are you calling it a non-HDD here? (fwiw, HDD _barely_ hits my acronym > cache anyway). > > How about this? > > /* > * Determine the locking method in use for this device. Return > * swap_cluster_info if SSD-style cluster-based locking is in place. > */ > static inline struct swap_cluster_info *lock_cluster_or_swap_info( > struct swap_info_struct *si, > unsigned long offset) > { > struct swap_cluster_info *ci; > > /* Try to use fine-grained SSD-style locking if available: */ > ci = lock_cluster(si, offset); > > /* Otherwise, fall back to traditional, coarse locking: */ > if (!ci) > spin_lock(&si->lock); > > return ci; > } This is better than my one, will use this. Thanks! > Which reminds me? Why do we even bother having two locking models? Because si->cluster_info is NULL for non-SSD, so we cannot use cluster lock. About why not use struct swap_cluster_info for non-SSD? Per my understanding, struct swap_cluster_info is optimized for SSD. Especially it assumes seeking is cheap. So different free swap slot scanning policy is used for SSD and non-SSD. Best Regards, Huang, Ying
next prev parent reply other threads:[~2018-07-18 3:09 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-07-17 0:55 [PATCH v2 0/7] swap: THP optimizing refactoring Huang, Ying 2018-07-17 0:55 ` [PATCH v2 1/7] swap: Add comments to lock_cluster_or_swap_info() Huang, Ying 2018-07-17 18:27 ` Dave Hansen 2018-07-18 3:09 ` Huang, Ying [this message] 2018-07-18 3:09 ` Huang, Ying 2018-07-17 0:55 ` [PATCH v2 2/7] mm/swapfile.c: Replace some #ifdef with IS_ENABLED() Huang, Ying 2018-07-17 18:32 ` Dave Hansen 2018-07-18 3:25 ` Huang, Ying 2018-07-18 3:25 ` Huang, Ying 2018-07-18 15:15 ` Dave Hansen 2018-07-19 4:42 ` Huang, Ying 2018-07-19 4:42 ` Huang, Ying 2018-07-17 0:55 ` [PATCH v2 3/7] swap: Use swap_count() in swap_page_trans_huge_swapped() Huang, Ying 2018-07-17 0:55 ` [PATCH v2 4/7] swap: Unify normal/huge code path " Huang, Ying 2018-07-17 0:55 ` [PATCH v2 5/7] swap: Unify normal/huge code path in put_swap_page() Huang, Ying 2018-07-17 0:55 ` [PATCH v2 6/7] swap: Add __swap_entry_free_locked() Huang, Ying 2018-07-17 0:55 ` [PATCH v2 7/7] swap, put_swap_page: Share more between huge/normal code path Huang, Ying 2018-07-17 18:36 ` Dave Hansen 2018-07-18 2:56 ` Huang, Ying 2018-07-18 2:56 ` Huang, Ying 2018-07-18 15:13 ` Dave Hansen 2018-07-17 15:17 ` [PATCH v2 0/7] swap: THP optimizing refactoring Daniel Jordan 2018-07-18 2:56 ` Huang, Ying 2018-07-18 2:56 ` Huang, Ying
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=87bmb5gryy.fsf@yhuang-dev.intel.com \ --to=ying.huang@intel.com \ --cc=akpm@linux-foundation.org \ --cc=dan.j.williams@intel.com \ --cc=daniel.m.jordan@oracle.com \ --cc=dave.hansen@linux.intel.com \ --cc=hannes@cmpxchg.org \ --cc=hughd@google.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mhocko@suse.com \ --cc=minchan@kernel.org \ --cc=riel@redhat.com \ --cc=shli@kernel.org \ /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.