Hi,

I've just been reviewing the file access code and starting to implement
a mechanism for striping multiple RRDs into one big file, to further
reduce IO load.

There are various functions in rrd_open.c (e.g. rrd_read, rrd_write)
that can be abstracted to do what is required.

However, I notice that some other files (e.g. rrd_create.c) also have
code which accesses files directly (e.g. calling open() to create a
file).

Is there some ongoing work to centralise the file access code?  Would it
be worthwhile for me to patch some of this code (e.g. rrd_create.c) to
go through the functions in rrd_open.c, or is there some other solution
coming?

Regards,

Daniel
_______________________________________________

This e-mail may contain information that is confidential, privileged or 
otherwise protected from disclosure. If you are not an intended recipient of 
this e-mail, do not duplicate or redistribute it by any means. Please delete it 
and any attachments and notify the sender that you have received it in error. 
Unless specifically indicated, this e-mail is not an offer to buy or sell or a 
solicitation to buy or sell any securities, investment products or other 
financial product or service, an official confirmation of any transaction, or 
an official statement of Barclays. Any views or opinions presented are solely 
those of the author and do not necessarily represent those of Barclays. This 
e-mail is subject to terms available at the following link: 
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the 
foregoing.  Barclays Capital is the investment banking division of Barclays 
Bank PLC, a company registered in England (number 1026167) with its registered 
offic
 e at 1 Churchill Place, London, E14 5HP.  This email may relate to or be sent 
from other members of the Barclays Group.
_______________________________________________

_______________________________________________
rrd-developers mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/rrd-developers

Reply via email to