[RFC] python-btrfs: getting arch dependent ioctl handling right

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

since I'd like to have my python btrfs library work correctly for users
with other systems than amd64, I have been looking at IOCTL number
generation a bit.

I just made something up in a branch, which follows the same way in
which the IOC defines in kernel source are done:

https://github.com/knorrie/python-btrfs/commits/ioctl

The only other hardware than amd64 I have is a raspberry pi, which
doesn't even seem to fall into the category having exceptions to the
defaults...

So, my question is:

1. am I still doing it wrong, or is this going into the right direction?

2. can you please test this branch if you have access to any of 'alpha',
'mips', 'powerpc', 'sparc', 'parisc' which runs a btrfs filesystem and
let me know if this makes it possible to use the library (e.g. run some
examples from the examples/ dir)

3. I also understand that there are difficulties for users who user 32
bit userland with a 64 bit kernel.
 - What is the exact technical reason for this?
 - What's the general opinion about this usecase? (needs to work, or,
"doctor, if I push here it hurts; well, don't push there"...)

Thanks,

-- 
Hans van Kranenburg
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux