From: Ingo Molnar <mingo@kernel.org>
To: NeilBrown <neilb@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
David Howells <dhowells@redhat.com>,
Steven Whitehouse <swhiteho@redhat.com>,
dm-devel@redhat.com, Chris Mason <clm@fb.com>,
Josef Bacik <jbacik@fb.com>, Steve French <sfrench@samba.org>,
Theodore Ts'o <tytso@mit.edu>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Ingo Molnar <mingo@redhat.com>,
Roland McGrath <roland@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
Date: Thu, 5 Jun 2014 14:45:09 +0200 [thread overview]
Message-ID: <20140605124509.GA1975@gmail.com> (raw)
In-Reply-To: <20140522195056.445f2dcb@notabene.brown>
* NeilBrown <neilb@suse.de> wrote:
> On Thu, 22 May 2014 11:05:02 +0200 Ingo Molnar <mingo@kernel.org> wrote:
>
> >
> > * NeilBrown <neilb@suse.de> wrote:
> >
> > > [[ get_maintainer.pl suggested 61 email address for this patch.
> > > I've trimmed that list somewhat. Hope I didn't miss anyone
> > > important...
> > > I'm hoping it will go in through the scheduler tree, but would
> > > particularly like an Acked-by for the fscache parts. Other acks
> > > welcome.
> > > ]]
> > >
> > > The current "wait_on_bit" interface requires an 'action' function
> > > to be provided which does the actual waiting.
> > > There are over 20 such functions, many of them identical.
> > > Most cases can be satisfied by one of just two functions, one
> > > which uses io_schedule() and one which just uses schedule().
> > >
> > > So:
> > > Rename wait_on_bit and wait_on_bit_lock to
> > > wait_on_bit_action and wait_on_bit_lock_action
> > > to make it explicit that they need an action function.
> > >
> > > Introduce new wait_on_bit{,_lock} and wait_on_bit{,_lock}_io
> > > which are *not* given an action function but implicitly use
> > > a standard one.
> > > The decision to error-out if a signal is pending is now made
> > > based on the 'mode' argument rather than being encoded in the action
> > > function.
> >
> > this patch fails to build on x86-32 allyesconfigs.
>
> Could you share the build errors?
Sure, find it attached below.
> >
> > Could we keep the old names for a while, and remove them in the next
> > cycle or so?
>
> I don't see how changing the names later rather than now will reduce the
> chance of errors... maybe I'm missing something.
Well, it would reduce build errors?
Thanks,
Ingo
====================>
fs/cifs/file.c: In function ‘cifs_oplock_break’:
fs/cifs/file.c:3652:4: warning: passing argument 3 of ‘wait_on_bit’ makes integer from pointer without a cast [enabled by default]
cifs_pending_writers_wait, TASK_UNINTERRUPTIBLE);
^
In file included from include/linux/fs.h:6:0,
from fs/cifs/file.c:24:
include/linux/wait.h:878:1: note: expected ‘unsigned int’ but argument is of type ‘int (*)(void *)’
wait_on_bit(void *word, int bit, unsigned mode)
^
fs/cifs/file.c:3652:4: error: too many arguments to function ‘wait_on_bit’
cifs_pending_writers_wait, TASK_UNINTERRUPTIBLE);
^
In file included from include/linux/fs.h:6:0,
from fs/cifs/file.c:24:
include/linux/wait.h:878:1: note: declared here
wait_on_bit(void *word, int bit, unsigned mode)
^
CC kernel/smp.o
CC kernel/trace/trace_event_perf.o
make[2]: *** [fs/cifs/file.o] Error 1
make[2]: *** Waiting for unfinished jobs....
CC drivers/bcma/sprom.o
CC fs/btrfs/locking.o
LD sound/isa/ad1848/snd-ad1848.o
LD sound/isa/ad1848/built-in.o
CC sound/isa/cs423x/cs4231.o
CC lib/fonts/fonts.o
CC lib/fonts/font_sun8x16.o
CC drivers/bcma/driver_chipcommon.o
CC lib/fonts/font_sun12x22.o
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: NeilBrown <neilb@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
David Howells <dhowells@redhat.com>,
Steven Whitehouse <swhiteho@redhat.com>,
dm-devel@redhat.com, Chris Mason <clm@fb.com>,
Josef Bacik <jbacik@fb.com>, Steve French <sfrench@samba.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Ingo Molnar <mingo@redhat.com>,
Roland McGrath <roland@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
Date: Thu, 5 Jun 2014 14:45:09 +0200 [thread overview]
Message-ID: <20140605124509.GA1975@gmail.com> (raw)
In-Reply-To: <20140522195056.445f2dcb@notabene.brown>
* NeilBrown <neilb@suse.de> wrote:
> On Thu, 22 May 2014 11:05:02 +0200 Ingo Molnar <mingo@kernel.org> wrote:
>
> >
> > * NeilBrown <neilb@suse.de> wrote:
> >
> > > [[ get_maintainer.pl suggested 61 email address for this patch.
> > > I've trimmed that list somewhat. Hope I didn't miss anyone
> > > important...
> > > I'm hoping it will go in through the scheduler tree, but would
> > > particularly like an Acked-by for the fscache parts. Other acks
> > > welcome.
> > > ]]
> > >
> > > The current "wait_on_bit" interface requires an 'action' function
> > > to be provided which does the actual waiting.
> > > There are over 20 such functions, many of them identical.
> > > Most cases can be satisfied by one of just two functions, one
> > > which uses io_schedule() and one which just uses schedule().
> > >
> > > So:
> > > Rename wait_on_bit and wait_on_bit_lock to
> > > wait_on_bit_action and wait_on_bit_lock_action
> > > to make it explicit that they need an action function.
> > >
> > > Introduce new wait_on_bit{,_lock} and wait_on_bit{,_lock}_io
> > > which are *not* given an action function but implicitly use
> > > a standard one.
> > > The decision to error-out if a signal is pending is now made
> > > based on the 'mode' argument rather than being encoded in the action
> > > function.
> >
> > this patch fails to build on x86-32 allyesconfigs.
>
> Could you share the build errors?
Sure, find it attached below.
> >
> > Could we keep the old names for a while, and remove them in the next
> > cycle or so?
>
> I don't see how changing the names later rather than now will reduce the
> chance of errors... maybe I'm missing something.
Well, it would reduce build errors?
Thanks,
Ingo
====================>
fs/cifs/file.c: In function ‘cifs_oplock_break’:
fs/cifs/file.c:3652:4: warning: passing argument 3 of ‘wait_on_bit’ makes integer from pointer without a cast [enabled by default]
cifs_pending_writers_wait, TASK_UNINTERRUPTIBLE);
^
In file included from include/linux/fs.h:6:0,
from fs/cifs/file.c:24:
include/linux/wait.h:878:1: note: expected ‘unsigned int’ but argument is of type ‘int (*)(void *)’
wait_on_bit(void *word, int bit, unsigned mode)
^
fs/cifs/file.c:3652:4: error: too many arguments to function ‘wait_on_bit’
cifs_pending_writers_wait, TASK_UNINTERRUPTIBLE);
^
In file included from include/linux/fs.h:6:0,
from fs/cifs/file.c:24:
include/linux/wait.h:878:1: note: declared here
wait_on_bit(void *word, int bit, unsigned mode)
^
CC kernel/smp.o
CC kernel/trace/trace_event_perf.o
make[2]: *** [fs/cifs/file.o] Error 1
make[2]: *** Waiting for unfinished jobs....
CC drivers/bcma/sprom.o
CC fs/btrfs/locking.o
LD sound/isa/ad1848/snd-ad1848.o
LD sound/isa/ad1848/built-in.o
CC sound/isa/cs423x/cs4231.o
CC lib/fonts/fonts.o
CC lib/fonts/font_sun8x16.o
CC drivers/bcma/driver_chipcommon.o
CC lib/fonts/font_sun12x22.o
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: NeilBrown <neilb@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
Oleg Nesterov <oleg@redhat.com>,
David Howells <dhowells@redhat.com>,
Steven Whitehouse <swhiteho@redhat.com>,
dm-devel@redhat.com, Chris Mason <clm@fb.com>,
Josef Bacik <jbacik@fb.com>, Steve French <sfrench@samba.org>,
Theodore Ts'o <tytso@mit.edu>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Ingo Molnar <mingo@redhat.com>,
Roland McGrath <roland@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] SCHED: remove proliferation of wait_on_bit action functions.
Date: Thu, 5 Jun 2014 14:45:09 +0200 [thread overview]
Message-ID: <20140605124509.GA1975@gmail.com> (raw)
In-Reply-To: <20140522195056.445f2dcb@notabene.brown>
* NeilBrown <neilb@suse.de> wrote:
> On Thu, 22 May 2014 11:05:02 +0200 Ingo Molnar <mingo@kernel.org> wrote:
>
> >
> > * NeilBrown <neilb@suse.de> wrote:
> >
> > > [[ get_maintainer.pl suggested 61 email address for this patch.
> > > I've trimmed that list somewhat. Hope I didn't miss anyone
> > > important...
> > > I'm hoping it will go in through the scheduler tree, but would
> > > particularly like an Acked-by for the fscache parts. Other acks
> > > welcome.
> > > ]]
> > >
> > > The current "wait_on_bit" interface requires an 'action' function
> > > to be provided which does the actual waiting.
> > > There are over 20 such functions, many of them identical.
> > > Most cases can be satisfied by one of just two functions, one
> > > which uses io_schedule() and one which just uses schedule().
> > >
> > > So:
> > > Rename wait_on_bit and wait_on_bit_lock to
> > > wait_on_bit_action and wait_on_bit_lock_action
> > > to make it explicit that they need an action function.
> > >
> > > Introduce new wait_on_bit{,_lock} and wait_on_bit{,_lock}_io
> > > which are *not* given an action function but implicitly use
> > > a standard one.
> > > The decision to error-out if a signal is pending is now made
> > > based on the 'mode' argument rather than being encoded in the action
> > > function.
> >
> > this patch fails to build on x86-32 allyesconfigs.
>
> Could you share the build errors?
Sure, find it attached below.
> >
> > Could we keep the old names for a while, and remove them in the next
> > cycle or so?
>
> I don't see how changing the names later rather than now will reduce the
> chance of errors... maybe I'm missing something.
Well, it would reduce build errors?
Thanks,
Ingo
====================>
fs/cifs/file.c: In function a??cifs_oplock_breaka??:
fs/cifs/file.c:3652:4: warning: passing argument 3 of a??wait_on_bita?? makes integer from pointer without a cast [enabled by default]
cifs_pending_writers_wait, TASK_UNINTERRUPTIBLE);
^
In file included from include/linux/fs.h:6:0,
from fs/cifs/file.c:24:
include/linux/wait.h:878:1: note: expected a??unsigned inta?? but argument is of type a??int (*)(void *)a??
wait_on_bit(void *word, int bit, unsigned mode)
^
fs/cifs/file.c:3652:4: error: too many arguments to function a??wait_on_bita??
cifs_pending_writers_wait, TASK_UNINTERRUPTIBLE);
^
In file included from include/linux/fs.h:6:0,
from fs/cifs/file.c:24:
include/linux/wait.h:878:1: note: declared here
wait_on_bit(void *word, int bit, unsigned mode)
^
CC kernel/smp.o
CC kernel/trace/trace_event_perf.o
make[2]: *** [fs/cifs/file.o] Error 1
make[2]: *** Waiting for unfinished jobs....
CC drivers/bcma/sprom.o
CC fs/btrfs/locking.o
LD sound/isa/ad1848/snd-ad1848.o
LD sound/isa/ad1848/built-in.o
CC sound/isa/cs423x/cs4231.o
CC lib/fonts/fonts.o
CC lib/fonts/font_sun8x16.o
CC drivers/bcma/driver_chipcommon.o
CC lib/fonts/font_sun12x22.o
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-06-05 12:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 2:37 [PATCH] SCHED: remove proliferation of wait_on_bit action functions NeilBrown
2014-05-01 7:42 ` Peter Zijlstra
2014-05-01 7:42 ` Peter Zijlstra
2014-05-01 9:26 ` NeilBrown
2014-05-01 9:31 ` Peter Zijlstra
2014-05-01 9:31 ` Peter Zijlstra
2014-05-13 16:06 ` David Howells
2014-05-13 16:06 ` David Howells
2014-05-13 16:45 ` Peter Zijlstra
2014-05-13 16:45 ` Peter Zijlstra
2014-05-13 16:08 ` David Howells
2014-05-13 16:08 ` David Howells
2014-05-19 13:08 ` [tip:sched/core] sched: Remove " tip-bot for NeilBrown
2014-05-22 9:05 ` [PATCH] SCHED: remove " Ingo Molnar
2014-05-22 9:05 ` Ingo Molnar
2014-05-22 9:50 ` NeilBrown
2014-06-05 12:45 ` Ingo Molnar [this message]
2014-06-05 12:45 ` Ingo Molnar
2014-06-05 12:45 ` Ingo Molnar
2014-06-06 0:23 ` NeilBrown
2014-06-06 6:04 ` Ingo Molnar
2014-06-06 6:04 ` Ingo Molnar
2014-07-02 1:28 ` NeilBrown
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=20140605124509.GA1975@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dhowells@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jbacik@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neilb@suse.de \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=roland@redhat.com \
--cc=sfrench@samba.org \
--cc=swhiteho@redhat.com \
--cc=trond.myklebust@primarydata.com \
--cc=tytso@mit.edu \
/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.