All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: [PATCH 1/2] [fs-devel] the real needs of just_schedule
Date: Thu, 08 May 2008 14:11:52 +0100	[thread overview]
Message-ID: <1210252312.3635.484.camel@quoit> (raw)
In-Reply-To: <1210096264-27426-1-git-send-email-crquan@gmail.com>

Hi,

On Wed, 2008-05-07 at 01:51 +0800, Denis Cheng wrote:
> there are some situations which really need a just schedule,
> with int return value;
> and this should be moved into lib/ in the future.
> 
> Signed-off-by: Denis Cheng <crquan@gmail.com>
> ---
>  fs/inode.c                |    2 +-
>  include/linux/writeback.h |   16 ++++++++++++----
>  2 files changed, 13 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/inode.c b/fs/inode.c
> index bf64781..b355a44 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -1291,7 +1291,7 @@ int inode_needs_sync(struct inode *inode)
>  
>  EXPORT_SYMBOL(inode_needs_sync);
>  
> -int inode_wait(void *word)
> +int just_schedule(void *word)
>  {
>  	schedule();
>  	return 0;
> diff --git a/include/linux/writeback.h b/include/linux/writeback.h
> index f462439..80ff5eb 100644
> --- a/include/linux/writeback.h
> +++ b/include/linux/writeback.h
> @@ -67,23 +67,31 @@ struct writeback_control {
>  
>  /*
>   * fs/fs-writeback.c
> - */	
> + */
>  void writeback_inodes(struct writeback_control *wbc);
> -int inode_wait(void *);
>  void sync_inodes_sb(struct super_block *, int wait);
>  void sync_inodes(int wait);
>  
> +/*
> + * fs/inode.c
> + *
> + * there are some situations which really need a just schedule,
> + * with int return value;
> + * and this should be moved into lib/ in the future.
> + */
> +int just_schedule(void *);
> +
Why is now not a good time? :-)

The patches look ok to me otherwise, but I wonder whether I should put
them in my tree (since they affect core code) or whether they'd be
better in -mm and/or linux-next?

Steve.




WARNING: multiple messages have this Message-ID (diff)
From: Steven Whitehouse <swhiteho@redhat.com>
To: Denis Cheng <crquan@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel@vger.kernel.org, cluster-devel@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] [fs-devel] the real needs of just_schedule
Date: Thu, 08 May 2008 14:11:52 +0100	[thread overview]
Message-ID: <1210252312.3635.484.camel@quoit> (raw)
In-Reply-To: <1210096264-27426-1-git-send-email-crquan@gmail.com>

Hi,

On Wed, 2008-05-07 at 01:51 +0800, Denis Cheng wrote:
> there are some situations which really need a just schedule,
> with int return value;
> and this should be moved into lib/ in the future.
> 
> Signed-off-by: Denis Cheng <crquan@gmail.com>
> ---
>  fs/inode.c                |    2 +-
>  include/linux/writeback.h |   16 ++++++++++++----
>  2 files changed, 13 insertions(+), 5 deletions(-)
> 
> diff --git a/fs/inode.c b/fs/inode.c
> index bf64781..b355a44 100644
> --- a/fs/inode.c
> +++ b/fs/inode.c
> @@ -1291,7 +1291,7 @@ int inode_needs_sync(struct inode *inode)
>  
>  EXPORT_SYMBOL(inode_needs_sync);
>  
> -int inode_wait(void *word)
> +int just_schedule(void *word)
>  {
>  	schedule();
>  	return 0;
> diff --git a/include/linux/writeback.h b/include/linux/writeback.h
> index f462439..80ff5eb 100644
> --- a/include/linux/writeback.h
> +++ b/include/linux/writeback.h
> @@ -67,23 +67,31 @@ struct writeback_control {
>  
>  /*
>   * fs/fs-writeback.c
> - */	
> + */
>  void writeback_inodes(struct writeback_control *wbc);
> -int inode_wait(void *);
>  void sync_inodes_sb(struct super_block *, int wait);
>  void sync_inodes(int wait);
>  
> +/*
> + * fs/inode.c
> + *
> + * there are some situations which really need a just schedule,
> + * with int return value;
> + * and this should be moved into lib/ in the future.
> + */
> +int just_schedule(void *);
> +
Why is now not a good time? :-)

The patches look ok to me otherwise, but I wonder whether I should put
them in my tree (since they affect core code) or whether they'd be
better in -mm and/or linux-next?

Steve.



  parent reply	other threads:[~2008-05-08 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-06 17:51 [Cluster-devel] [PATCH 1/2] [fs-devel] the real needs of just_schedule Denis Cheng
2008-05-06 17:51 ` Denis Cheng
2008-05-06 17:51 ` [Cluster-devel] [PATCH 2/2] [GFS2] remove the duplicates " Denis Cheng
2008-05-06 17:51   ` Denis Cheng
2008-05-08 13:11 ` Steven Whitehouse [this message]
2008-05-08 13:11   ` [PATCH 1/2] [fs-devel] the real needs " Steven Whitehouse
2008-05-08 18:30   ` [Cluster-devel] " rae l
2008-05-08 18:30     ` rae l

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=1210252312.3635.484.camel@quoit \
    --to=swhiteho@redhat.com \
    /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: link
Be 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.