Displaying 20 results from an estimated 225 matches for "blksizes".
Did you mean:
blksize
2019 May 13
0
[nbdkit PATCH v2 2/2] cache, cow: Reduce use of bounce-buffer
Although the time spent in memcpy/memset probably pales in comparison
to time spent in socket I/O, it's still worth worth reducing the
number of times we have to utilize a bounce buffer when we already
have aligned data.
Note that blocksize, cache, and cow all do block fragmentation and
bounce-buffer alignment; this brings the logic in cache and cow (which
were copied from one another) more
2019 May 13
3
[nbdkit PATCH v2 0/2] Bounce buffer cleanups
Based on Rich's review of my v1 that touched only cache.c, I have now
tried to bring all three filters with alignment rounding in line with
one another.
There is definitely room for future improvements once we teach nbdkit
to let filters and plugins advertise block sizes, but I'm hoping to
get NBD_CMD_CACHE implemented first.
Eric Blake (2):
blocksize: Process requests in linear order
2014 Apr 14
2
PXE booting UEFI
Good Afternoon,
As per the installation guide, section 30.2.2 I?ve created an efidefault file at /var/lib/tftpboot/pxelinux/pxelinux.cfg/efidefault
However, this file is never requested by the 64 bit PXE loader (bootx64.efi), as shown by tcpdump:
75 RRQ "/pxelinux/42272635-0011-5053-ACF2-82A100E615F2" octet tsize 0 blksize 512
59 RRQ "/pxelinux/01-00-50-56-A7-BA-BF"
2018 Jan 21
2
Re: [PATCH nbdkit] filters: Add copy-on-write filter.
Here's the patch (on top of the preceeding one) which uses a bitmap
instead of SEEK_DATA.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines. Supports shell scripting,
bindings from many languages. http://libguestfs.org
--4VrXvz3cwkc87Wze
2019 Jan 04
0
[PATCH nbdkit v5 3/3] cache: Implement cache-max-size and cache space reclaim.
The original plan was to have a background thread doing the reclaim.
However that cannot work given the design of filters, because a
background thread cannot access the next_ops struct which is only
available during requests.
Therefore we spread the work over the request threads. Each blk_*
function checks whether there is work to do, and if there is will
reclaim up to two blocks from the cache
2012 Aug 01
1
Erroneous operation not permitted when deleting mailbox with mdbox
I'm seeing the following error in our logs when removing mailboxes (we are using mdbox and dovecot 2.1.8):
Aug 1 20:03:36 msgsrv dovecot: imap(test at test.com): Error: stat(/mailstore/domains/test.com/test/mdbox/mailboxes/Spam) failed: Operation not permitted
Aug 1 20:03:36 msgsrv dovecot: imap(test at test.com): Mailbox deleted: Spam
When I run truss against the process it appears the
2019 May 11
2
[nbdkit PATCH] cache: Reduce use of bounce-buffer
Although the time spent in memcpy/memset probably pales in comparison
to time spent in socket I/O, it's still worth worth reducing the
number of times we have to utilize a bounce buffer when we already
have aligned data.
Signed-off-by: Eric Blake <eblake@redhat.com>
---
filters/cache/cache.c | 60 ++++++++++++++++++++++++++++---------------
1 file changed, 39 insertions(+), 21
2019 Jan 04
5
[PATCH nbdkit v5 3/3] cache: Implement cache-max-size and cache space reclaim.
v4:
https://www.redhat.com/archives/libguestfs/2019-January/msg00032.html
v5:
- Now we set the block size at run time.
I'd like to say that I was able to test this change, but
unfortunately I couldn't find any easy way to create a filesystem
on x86-64 with a block size > 4K. Ext4 doesn't support it at all,
and XFS doesn't support block size > page size (and I
2018 Jan 20
4
[PATCH nbdkit] filters: Add copy-on-write filter.
Eric, you'll probably find the design "interesting" ...
It does work, for me at least.
Rich.
2019 May 15
2
nbdkit problem with cache/cow and unaligned sizes
Right now, the cache and cow filters always round up requests to blksize
boundaries (blksize for cache is dynamically determined at connection
start, for cow is fixed as BLKSIZE). Which is fine for the bulk of the
underlying file, but can cause problems when reading past EOF for a
partial tail of an underlying plugin. We aren't validating that filter
calls to next_ops are within bounds; and
2013 Nov 04
3
syslinux.efi pxeboot across multiple subnets
Hello,
I am attempting to setup a PXE setup for a network using multiple subnets.
The current layout has dhcp on one subnet (10.16.215.8/30), tftp on another
(10.16.194.0/23), and the system to be installed on yet another subnet (
10.16.233.0/24 [there's actually about 30 different subnets the system to
be installed could be on]).
When I have the system to be installed on the same subnet as
2020 Jul 15
3
[PATCH] virtio-blk: check host supplied logical block size
Linux kernel only supports logical block sizes which are power of two,
at least 512 bytes and no more that PAGE_SIZE.
Check this instead of crashing later on.
Note that there is no need to check physical block size since it is
only a hint, and virtio-blk already only supports power of two values.
Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=1664619
Signed-off-by: Maxim Levitsky
2020 Jul 15
3
[PATCH] virtio-blk: check host supplied logical block size
Linux kernel only supports logical block sizes which are power of two,
at least 512 bytes and no more that PAGE_SIZE.
Check this instead of crashing later on.
Note that there is no need to check physical block size since it is
only a hint, and virtio-blk already only supports power of two values.
Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=1664619
Signed-off-by: Maxim Levitsky
2015 Oct 07
2
Hyper-V Gen 2 waiting for ldlinux.e64
Hi,
I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a PXE client (no physical machines available). This is a UEFI VM, and as per instructions I've read I have disabled secure boot on this VM for the installation of Linux. I am using the latest tftp-hpa package with the following config:
# /etc/default/tftpd-hpa
TFTP_USERNAME="tftp"
2010 Nov 11
1
blksize option in tftp client?
Been looking high and low for an option to request blksize in
the hpa tftp client but I cant find one. How do I
request a bigger blksize with the hpa tftp client?
Jocke
2018 Dec 02
2
[PATCH nbdkit v2] common: Move shared bitmap code to a common library.
This is exactly the same as v1:
https://www.redhat.com/archives/libguestfs/2018-December/msg00004.html
except that it now frees the bitmap on unload (which the old code did
not - there was always a memory leak).
Rich.
2018 Dec 03
1
Re: [PATCH nbdkit v2] common: Move shared bitmap code to a common library.
On 12/2/18 10:33 AM, Richard W.M. Jones wrote:
> The cow and cache filters both use a bitmap mapping virtual disk
> blocks to status stored in the bitmap. The implementation of the
> bitmaps is very similar because one was derived from the other when
> the filters were implemented.
>
> The main difference is the cow filter uses a simple bitmap (one bit
> per block), whereas
2008 Feb 08
2
pxelinux, pxe requesting bad filename from tftp
Hey,
I have a problem booting certain machines with pxelinux. I have
pxelinux.0 in the root of my tftp server and dhcp pointing to the right
location:
# dhcpd.conf
authoritative;
option domain-name "example.net";
ddns-update-style none;
default-lease-time 3600;
max-lease-time 86400;
subnet 10.0.0.0 netmask 255.255.255.0 {
range 10.0.0.3 10.0.0.20;
server-name
2014 Mar 11
2
syslinux.efi [PXELINUX EFI 64 boot] not properly TFTP'ing ldlinux.e64
Gene and co,
Now my pxelinux efi 64 boot is properly loading syslinux.efi (via TFTP)
It then issues a TFTP file request for efi.x64/pxelinux.cfg/ldlinux.e64.
(All my efi x64 content is under efi.x64/pxelinux.cfg).
However, I see that it fails to properly negotiate the TFTP options with my
TFTP server. so it never transfers ldlinux.e64 over.
In its file request packet, it asks for these TFTP
2020 Jul 15
2
[PATCH] virtio-blk: check host supplied logical block size
On Wed, 2020-07-15 at 06:06 -0400, Michael S. Tsirkin wrote:
> On Wed, Jul 15, 2020 at 12:55:18PM +0300, Maxim Levitsky wrote:
> > Linux kernel only supports logical block sizes which are power of
> > two,
> > at least 512 bytes and no more that PAGE_SIZE.
> >
> > Check this instead of crashing later on.
> >
> > Note that there is no need to check