Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-31 Thread Markus Pargmann
Hi, On Sat, Jan 31, 2015 at 03:43:16PM +0100, Andreas Klauer wrote: > On Sat, Jan 31, 2015 at 08:52:18AM -0500, Paul Clements wrote: > >The pid is also used to break a hung connection. See nbd_xmit_timeout. > > I'm using the pid to find the first free NBD device... > > If it's going away I

Re: [RFC 4/4] nbd: Add support for nbd as root device

2015-01-31 Thread Markus Pargmann
On Sat, Jan 31, 2015 at 08:52:18AM -0500, Paul Clements wrote: > On Saturday, January 31, 2015, Markus Pargmann wrote: > > > On Fri, Jan 30, 2015 at 06:30:14PM +0100, Wouter Verhelst wrote: > > > On Fri, Jan 30, 2015 at 09:04:00AM +0100, Markus Pargmann wrote: > > > > Hi, > > > > > > > > On Fri,

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-31 Thread Andreas Klauer
On Sat, Jan 31, 2015 at 08:52:18AM -0500, Paul Clements wrote: >The pid is also used to break a hung connection. See nbd_xmit_timeout. I'm using the pid to find the first free NBD device... If it's going away I guess I'll have to stick to /proc/partitions...? Although last time I tried, it

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-31 Thread Markus Pargmann
On Fri, Jan 30, 2015 at 06:30:14PM +0100, Wouter Verhelst wrote: > On Fri, Jan 30, 2015 at 09:04:00AM +0100, Markus Pargmann wrote: > > Hi, > > > > On Fri, Jan 30, 2015 at 12:42:54AM +0100, Wouter Verhelst wrote: > > > Not that I'm opposed to this, but you do realize that doing nbd-client > > >

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-31 Thread Markus Pargmann
Hi, On Fri, Jan 30, 2015 at 10:10:55AM -0800, H. Peter Anvin wrote: > On 01/30/2015 12:04 AM, Markus Pargmann wrote: > > Yes, that was the first idea how to implement a complete netboot for an > > embedded ARM device. However, an initramfs is at least around 1MB in > > size... > > No, it's not.

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-31 Thread Markus Pargmann
Hi, On Sat, Jan 31, 2015 at 03:43:16PM +0100, Andreas Klauer wrote: On Sat, Jan 31, 2015 at 08:52:18AM -0500, Paul Clements wrote: The pid is also used to break a hung connection. See nbd_xmit_timeout. I'm using the pid to find the first free NBD device... If it's going away I guess

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-31 Thread Andreas Klauer
On Sat, Jan 31, 2015 at 08:52:18AM -0500, Paul Clements wrote: The pid is also used to break a hung connection. See nbd_xmit_timeout. I'm using the pid to find the first free NBD device... If it's going away I guess I'll have to stick to /proc/partitions...? Although last time I tried, it

Re: [RFC 4/4] nbd: Add support for nbd as root device

2015-01-31 Thread Markus Pargmann
On Sat, Jan 31, 2015 at 08:52:18AM -0500, Paul Clements wrote: On Saturday, January 31, 2015, Markus Pargmann m...@pengutronix.de wrote: On Fri, Jan 30, 2015 at 06:30:14PM +0100, Wouter Verhelst wrote: On Fri, Jan 30, 2015 at 09:04:00AM +0100, Markus Pargmann wrote: Hi, On Fri,

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-31 Thread Markus Pargmann
Hi, On Fri, Jan 30, 2015 at 10:10:55AM -0800, H. Peter Anvin wrote: On 01/30/2015 12:04 AM, Markus Pargmann wrote: Yes, that was the first idea how to implement a complete netboot for an embedded ARM device. However, an initramfs is at least around 1MB in size... No, it's not.

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-31 Thread Markus Pargmann
On Fri, Jan 30, 2015 at 06:30:14PM +0100, Wouter Verhelst wrote: On Fri, Jan 30, 2015 at 09:04:00AM +0100, Markus Pargmann wrote: Hi, On Fri, Jan 30, 2015 at 12:42:54AM +0100, Wouter Verhelst wrote: Not that I'm opposed to this, but you do realize that doing nbd-client from initramfs

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-30 Thread H. Peter Anvin
On 01/30/2015 12:04 AM, Markus Pargmann wrote: > Yes, that was the first idea how to implement a complete netboot for an > embedded ARM device. However, an initramfs is at least around 1MB in > size... No, it's not. -hpa -- To unsubscribe from this list: send the line "unsubscribe

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-30 Thread Wouter Verhelst
On Fri, Jan 30, 2015 at 09:04:00AM +0100, Markus Pargmann wrote: > Hi, > > On Fri, Jan 30, 2015 at 12:42:54AM +0100, Wouter Verhelst wrote: > > Not that I'm opposed to this, but you do realize that doing nbd-client > > from initramfs or similar is possible, right? Most initramfs > >

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-30 Thread Markus Pargmann
Hi, On Fri, Jan 30, 2015 at 12:42:54AM +0100, Wouter Verhelst wrote: > On Tue, Jan 13, 2015 at 02:44:25PM +0100, Markus Pargmann wrote: > > Adding support to nbd to use it as a root device. This code essentially > > provides a minimal nbd-client implementation within the kernel. It opens > > a

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-30 Thread Wouter Verhelst
On Fri, Jan 30, 2015 at 09:04:00AM +0100, Markus Pargmann wrote: Hi, On Fri, Jan 30, 2015 at 12:42:54AM +0100, Wouter Verhelst wrote: Not that I'm opposed to this, but you do realize that doing nbd-client from initramfs or similar is possible, right? Most initramfs implementations these

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-30 Thread H. Peter Anvin
On 01/30/2015 12:04 AM, Markus Pargmann wrote: Yes, that was the first idea how to implement a complete netboot for an embedded ARM device. However, an initramfs is at least around 1MB in size... No, it's not. -hpa -- To unsubscribe from this list: send the line unsubscribe

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-30 Thread Markus Pargmann
Hi, On Fri, Jan 30, 2015 at 12:42:54AM +0100, Wouter Verhelst wrote: On Tue, Jan 13, 2015 at 02:44:25PM +0100, Markus Pargmann wrote: Adding support to nbd to use it as a root device. This code essentially provides a minimal nbd-client implementation within the kernel. It opens a socket

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-29 Thread Wouter Verhelst
On Tue, Jan 13, 2015 at 02:44:25PM +0100, Markus Pargmann wrote: > Adding support to nbd to use it as a root device. This code essentially > provides a minimal nbd-client implementation within the kernel. It opens > a socket and makes the negotiation with the server. Afterwards it passes > the

Re: [Nbd] [RFC 4/4] nbd: Add support for nbd as root device

2015-01-29 Thread Wouter Verhelst
On Tue, Jan 13, 2015 at 02:44:25PM +0100, Markus Pargmann wrote: Adding support to nbd to use it as a root device. This code essentially provides a minimal nbd-client implementation within the kernel. It opens a socket and makes the negotiation with the server. Afterwards it passes the socket

Re: [RFC 4/4] nbd: Add support for nbd as root device

2015-01-20 Thread Markus Pargmann
On Tue, Jan 13, 2015 at 02:44:25PM +0100, Markus Pargmann wrote: > Adding support to nbd to use it as a root device. This code essentially > provides a minimal nbd-client implementation within the kernel. It opens > a socket and makes the negotiation with the server. Afterwards it passes > the

Re: [RFC 4/4] nbd: Add support for nbd as root device

2015-01-20 Thread Markus Pargmann
On Tue, Jan 13, 2015 at 02:44:25PM +0100, Markus Pargmann wrote: Adding support to nbd to use it as a root device. This code essentially provides a minimal nbd-client implementation within the kernel. It opens a socket and makes the negotiation with the server. Afterwards it passes the socket

[RFC 4/4] nbd: Add support for nbd as root device

2015-01-13 Thread Markus Pargmann
Adding support to nbd to use it as a root device. This code essentially provides a minimal nbd-client implementation within the kernel. It opens a socket and makes the negotiation with the server. Afterwards it passes the socket to the normal nbd-code to handle the connection. The arguments for

[RFC 4/4] nbd: Add support for nbd as root device

2015-01-13 Thread Markus Pargmann
Adding support to nbd to use it as a root device. This code essentially provides a minimal nbd-client implementation within the kernel. It opens a socket and makes the negotiation with the server. Afterwards it passes the socket to the normal nbd-code to handle the connection. The arguments for