Bug#717689: linux: please review and merge m68k patch

2013-07-25 Thread Ben Hutchings
On Thu, 2013-07-25 at 09:19 +0200, Wouter Verhelst wrote: > On 24-07-13 14:58, Ben Hutchings wrote: > > On Wed, 2013-07-24 at 12:06 +0200, Wouter Verhelst wrote: > >> On 24-07-13 04:10, Ben Hutchings wrote: > >> +CONFIG_NFS_SWAP=y > >>> > >>> Really? > >> > >> It _should_ be safe since the PF_M

Bug#717689: linux: please review and merge m68k patch

2013-07-25 Thread Wouter Verhelst
On 24-07-13 14:58, Ben Hutchings wrote: > On Wed, 2013-07-24 at 12:06 +0200, Wouter Verhelst wrote: >> On 24-07-13 04:10, Ben Hutchings wrote: >> +CONFIG_NFS_SWAP=y >>> >>> Really? >> >> It _should_ be safe since the PF_MEMALLOC patches were accepted >> (3.6-rc1, commit 7f338fe4540b and friends

Bug#717689: linux: please review and merge m68k patch

2013-07-24 Thread Geert Uytterhoeven
On Wed, Jul 24, 2013 at 9:34 AM, Thorsten Glaser wrote: >> > >> +## choice: Preemption Model > […] >> Now why do you want to change that? > > My naïve reasoning is like that: less preemption = less > interruption / context switches = more work done in total > at the cost of a bit interactivity (pr

Bug#717689: linux: please review and merge m68k patch

2013-07-24 Thread Ben Hutchings
On Wed, 2013-07-24 at 12:06 +0200, Wouter Verhelst wrote: > On 24-07-13 04:10, Ben Hutchings wrote: > +CONFIG_NFS_SWAP=y > > > > Really? > > It _should_ be safe since the PF_MEMALLOC patches were accepted > (3.6-rc1, commit 7f338fe4540b and friends). Haven't tested it myself > yet, though. >

Bug#717689: linux: please review and merge m68k patch

2013-07-24 Thread Thorsten Glaser
Dixi quod… >>Another thing that puzzles me: >> >>config SMC91X >>depends on (ARM || M32R || SUPERH || MIPS || BLACKFIN || \ >>MN10300 || COLDFIRE || ARM64) > >Maybe just an explicit || ATARI_ETHERNAT here? > >Add || ATARI_ETHERNEC to NE2000 as well I’d say, so everyone

Bug#717689: linux: please review and merge m68k patch

2013-07-24 Thread Wouter Verhelst
On 24-07-13 04:10, Ben Hutchings wrote: +CONFIG_NFS_SWAP=y > > Really? It _should_ be safe since the PF_MEMALLOC patches were accepted (3.6-rc1, commit 7f338fe4540b and friends). Haven't tested it myself yet, though. (and yes, I would say that swap over NBD will produce less overhead and is

Bug#717689: linux: please review and merge m68k patch

2013-07-24 Thread Thorsten Glaser
On Wed, 24 Jul 2013, Ben Hutchings wrote: [ ext2/3/4 ] > I think we may want to enable this at the top level later, but there is > no reason to override it now. OK, will remove that. > > >> +CONFIG_NFS_SWAP=y > > Really? Not? Is there something better? Hm, Wouter would probably say swap over n

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Ben Hutchings
On Tue, 2013-07-23 at 22:11 +, Thorsten Glaser wrote: [...] > >> -CONFIG_EXT4_USE_FOR_EXT23=y > > > >You could still stick to this option. > > The debian/config/config doesn’t use it and builds > separate ext2/ext3/ext4 modules instead, so I did > that too. I think we may want to enable this

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Thorsten Glaser
Dixi quod… >This is merely what we had before. (I’m giving nfeth a chance here…) “No such device” is what nfeth.ko says upon insmod. I’ll report this as bug upstream and revert it to =y too: --- debian/config/m68k/config 2013-07-23 22:38:05.519153764 + +++ - 2013-07-23 22:38:28.394235256

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Thorsten Glaser
Bastian Blank dixit: >On Tue, Jul 23, 2013 at 08:42:04PM +, Thorsten Glaser wrote: >> +CONFIG_IOSCHED_DEADLINE=m >> +CONFIG_IOSCHED_CFQ=m > >Should be configured in the top config. They’re =y there. I put them into modules to save space. >> +# CONFIG_EXT2_FS_SECURITY is not set >> +# CONFIG_

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Thorsten Glaser
Bastian Blank dixit: >On Tue, Jul 23, 2013 at 09:26:28PM +, Thorsten Glaser wrote: >> Which package is responsible for the inclusion of arch-specific >> kernel modules into the initrd (for MODULES=most right now; I >> have yet to try MODULES=dep)? > >initramfs-tools OK, thanks! Doesn’t help

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Bastian Blank
On Tue, Jul 23, 2013 at 08:42:04PM +, Thorsten Glaser wrote: > +CONFIG_IOSCHED_DEADLINE=m > +CONFIG_IOSCHED_CFQ=m Should be configured in the top config. > +# CONFIG_EXT2_FS_SECURITY is not set > +# CONFIG_EXT3_FS_SECURITY is not set Why? > -CONFIG_EXT4_FS=y > -CONFIG_EXT4_USE_FOR_EXT23=y

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Bastian Blank
On Tue, Jul 23, 2013 at 09:26:28PM +, Thorsten Glaser wrote: > Which package is responsible for the inclusion of arch-specific > kernel modules into the initrd (for MODULES=most right now; I > have yet to try MODULES=dep)? initramfs-tools Bastian -- Violence in reality is quite different fr

Bug#717689: linux: please review and merge m68k patch

2013-07-23 Thread Thorsten Glaser
Dixi quod… >Even if this may have some minor issues still, it’ll be better >than building kernel images that fail to boot at all, that’s why Ah well. Of course it didn’t boot. /lib/modules/3.10-0+m68k.2-m68k/kernel/arch/m68k/emu/nfblock.ko is the “IDE” driver for ARAnyM machines (like virtio-blk