Re: BPF memstore and bpf_validate_ext()

2013-12-10 Thread Alexander Nasonov
Mindaugas Rasiukevicius wrote:
 Alexander Nasonov al...@yandex.ru wrote:
  In your case BPF_COP is always the first instruction (or in the
  first linear block). Because it's the first and it's a function
  call, it can be moved outside of bpf program and inlined.
  
  If this is the case, you don't need BPF_COP at all.
 
 For this particular case - yes, correct.
 
  Except of course you may run out or memwords one day and you want
  to have BPF_COP as a fallback.
 
 I still need BPF_COP for other tasks (e.g. NPF_COP_TABLE).  Running out
 of words is unlikely, but COP can certainly be used to handle that too.

I wonder why do you need two different features when one is a
superset of the other if you could use BPF_COP? If the only reason
is performance, external memory is not a win-win proposition.

PS sljit has a non-standard fast call mechanism. If you're really
concerned about performance, you can generate copfuncs and I can
call them from bpfjit.

Alex


SAS tape drives

2013-12-10 Thread Mark Davies
Are SAS tape drives supported in NetBSD?

I have an LSI MegaRAID SAS card with an HP LTO5 SAS drive attached.  
The card's WebBIOS can see the tape attached and NetBSD can see the 
LSI card but NetBSD show no evidence of seeing the tape drive (not 
even as an unconfigured device).

cheers
mark


Re: SAS tape drives

2013-12-10 Thread Eduardo Horvath
On Wed, 11 Dec 2013, Mark Davies wrote:

 Are SAS tape drives supported in NetBSD?
 
 I have an LSI MegaRAID SAS card with an HP LTO5 SAS drive attached.  
 The card's WebBIOS can see the tape attached and NetBSD can see the 
 LSI card but NetBSD show no evidence of seeing the tape drive (not 
 even as an unconfigured device).

Last time I fiddled around with the LSI MegaRAID stack it did not provide 
any sort of transparent access to attached devices.  Can you create a LUN 
with the tape device?  

You might have more success with the LSI MPT stack.  That at least 
provides transparent access to the target devices.  I don't know whether 
mpt hooks into NetBSD's scsipi layer in a way that it will attach non-disk 
devices, but I suspect it would.

Eduardo


Re: SAS tape drives

2013-12-10 Thread Mark Davies
On Wed, 11 Dec 2013, Eduardo Horvath wrote:
 Last time I fiddled around with the LSI MegaRAID stack it did not
 provide any sort of transparent access to attached devices.  Can
 you create a LUN with the tape device?
 
 You might have more success with the LSI MPT stack.  That at least
 provides transparent access to the target devices.  I don't know
 whether mpt hooks into NetBSD's scsipi layer in a way that it will
 attach non-disk devices, but I suspect it would.

I used the MegaRAID card as that was what we had lying around but I 
could buy something else.

I found this: 
https://www.ascent.co.nz/productspecification.aspx?ItemID=413461
but that seems to use the mps driver on FreeBSD and NetBSD doesn't 
have it.  Any guess on how hard it would be to port?

cheers
mark


Re: SAS tape drives

2013-12-10 Thread Manuel Bouyer
On Wed, Dec 11, 2013 at 04:55:12PM +1300, Mark Davies wrote:
 On Wed, 11 Dec 2013, Eduardo Horvath wrote:
  Last time I fiddled around with the LSI MegaRAID stack it did not
  provide any sort of transparent access to attached devices.  Can
  you create a LUN with the tape device?
  
  You might have more success with the LSI MPT stack.  That at least
  provides transparent access to the target devices.  I don't know
  whether mpt hooks into NetBSD's scsipi layer in a way that it will
  attach non-disk devices, but I suspect it would.
 
 I used the MegaRAID card as that was what we had lying around but I 
 could buy something else.
 
 I found this: 
 https://www.ascent.co.nz/productspecification.aspx?ItemID=413461
 but that seems to use the mps driver on FreeBSD and NetBSD doesn't 
 have it.  Any guess on how hard it would be to port?

Hopefully it's supported by our mpii(4) driver.


-- 
Manuel Bouyer bou...@antioche.eu.org
 NetBSD: 26 ans d'experience feront toujours la difference
--