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

[Xen-devel] blkif shared ring


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Samvel Yuri <samvelox@xxxxxxxxx>
  • Date: Tue, 18 Nov 2008 15:29:48 -0800 (PST)
  • Delivery-date: Tue, 18 Nov 2008 15:30:20 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=k8aXo8HzlfIjof77zPjXRXer3+J4Xn/RfR8NlOEz2dwz7BQ6jDsUfCrKh4perdLP1hqnGFKgcqFTWHa70ufiDqsdGMcu1ZsgE+ohuXNOfR8goSiBhdgK0YDSt8pvuKnC373sZ8zaRMxXiEYIZrvJTS7qeH97eNa7L3/WllXzuKk=;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello,

With xen 3.3.0 version, I understand that by increasing blkif_reqs you
possibly speed up writes by being able to write whole of tracks. And,
shared ring size is 64 between blkfront & blkback to fit in a page of
size PAGE_SIZE. Both blkfront & blkback accomodate shared ring within
a page size.

Wouldn't the shared ring be likely a bottleneck in very large number
os IOs, have anybody ran into such issue?

Is there a reason to _always_ accomodate ring buffer in a page? How
can I increase the shared ring size between blkfront & blkback?

Do you have any suggestions/recommendations?

thanks,
~Sam


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.