Prev: [PATCH 08/20] epca: Kill the big kernel lock
Next: [PATCHv4 0/8] The FunctionFS composite function
From: Alan Cox on 5 May 2010 06:50
On Wed, 5 May 2010 00:33:39 +0200
Arnd Bergmann <arnd(a)arndb.de> wrote:

> This is the second attempt to get the BKL out of the
> TTY code. I've updated the patches to be based on top
> of Alan's series and improved a number of things.

I've updated the patches I first sent out with the fixes for the problems
you found and send out a new set.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Arnd Bergmann on 5 May 2010 08:30
On Wednesday 05 May 2010, Alan Cox wrote:
> On Wed, 5 May 2010 00:33:39 +0200
> Arnd Bergmann <arnd(a)arndb.de> wrote:
>
> > This is the second attempt to get the BKL out of the
> > TTY code. I've updated the patches to be based on top
> > of Alan's series and improved a number of things.
>
> I've updated the patches I first sent out with the fixes for the problems
> you found and send out a new set.

Ok, I've rebased my patches on top of those now and pushed to
git.kernel.org:/pub/scm/linux/kernel/git/arnd/playground.git#bkl/tty,
minus my patch 13/13, which I already mentioned was broken.

Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Alan Cox on 17 May 2010 09:40
On Sat, 15 May 2010 22:59:46 +0200
Arnd Bergmann <arnd(a)arndb.de> wrote:

> This is the third attempt to get the BKL out of the
> TTY code. This version goes much further than the
> previous one, and eliminates most of the code I
> had introduced there.

At this point I think the only way to make further progress is to
actually push this stuff into the kernel on top of the BKL removal
patches for the drivers and see what happens. Something will no doubt
break but we can try and nail them in time or if not revert the series
and try again next kernel.

The big nasty remaining after this is drivers/serial, which probably
wants some serious reconstructive surgery to use kfifo etc. Either way
its an independent problem to the stuff this lot tackles.

So this series

Acked-by: Alan Cox <alan(a)linux.intel.com>

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Greg KH on 17 May 2010 11:40
On Mon, May 17, 2010 at 02:41:30PM +0100, Alan Cox wrote:
> On Sat, 15 May 2010 22:59:46 +0200
> Arnd Bergmann <arnd(a)arndb.de> wrote:
>
> > This is the third attempt to get the BKL out of the
> > TTY code. This version goes much further than the
> > previous one, and eliminates most of the code I
> > had introduced there.
>
> At this point I think the only way to make further progress is to
> actually push this stuff into the kernel on top of the BKL removal
> patches for the drivers and see what happens. Something will no doubt
> break but we can try and nail them in time or if not revert the series
> and try again next kernel.
>
> The big nasty remaining after this is drivers/serial, which probably
> wants some serious reconstructive surgery to use kfifo etc. Either way
> its an independent problem to the stuff this lot tackles.
>
> So this series
>
> Acked-by: Alan Cox <alan(a)linux.intel.com>

I'd prefer to do this for .36, not for .35. Arnd, I'll be glad to queue
these patches up to the tty development tree after .35-rc1 is out, so it
gets lots of testing in the linux-next tree, is that ok? If so, can you
resend them to me at that time?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
From: Arnd Bergmann on 17 May 2010 15:00
On Monday 17 May 2010, Greg KH wrote:
>
> I'd prefer to do this for .36, not for .35. Arnd, I'll be glad to queue
> these patches up to the tty development tree after .35-rc1 is out, so it
> gets lots of testing in the linux-next tree, is that ok? If so, can you
> resend them to me at that time?

Ok, I'll make sure it still works with .35-rc1 when it's out and add
Alan's ACK, then send a you a pull request. Did you already merge the
series from Alan that this is based on, or do you want those patches
to wait as well? They are in my git tree, so they will be included
in my pull request if they are not in -rc1.

Also, it would be nice if you could merge the first patch of my
series, which should be completely harmless (it just renames
function calls) but having it upstream means that we can
keep the remaining patches that are required for BKL-less
kernels a lot smaller.

Arnd

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 |  Next  |  Last
Pages: 1 2 3
Prev: [PATCH 08/20] epca: Kill the big kernel lock
Next: [PATCHv4 0/8] The FunctionFS composite function