[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87wotqvjit.fsf@yhuang-dev.intel.com>
Date: Fri, 20 Jul 2018 08:27:22 +0800
From: "Huang\, Ying" <ying.huang@...el.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>, Michal Hocko <mhocko@...e.com>,
"Johannes Weiner" <hannes@...xchg.org>,
Shaohua Li <shli@...nel.org>, Hugh Dickins <hughd@...gle.com>,
Minchan Kim <minchan@...nel.org>,
Rik van Riel <riel@...hat.com>,
Dan Williams <dan.j.williams@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>
Subject: Re: [PATCH v3 1/8] swap: Add comments to lock_cluster_or_swap_info()
Christoph Hellwig <hch@...radead.org> writes:
> On Thu, Jul 19, 2018 at 04:48:35PM +0800, Huang Ying wrote:
>> +/*
>> + * 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: */
>
> Once you touch this are can you also please use standard two-tab
> alignment for the spill-over function arguments:
>
> static inline struct swap_cluster_info *lock_cluster_or_swap_info(
> struct swap_info_struct *si, unsigned long offset)
Sure. Will change this in next version.
Best Regards,
Huang, Ying
Powered by blists - more mailing lists