[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fuse-devel
Subject:    Re: [fuse-devel] FUSE lseek flags
From:       Tomas_Dalebjörk <tomas.dalebjork () gmail ! com>
Date:       2019-12-11 7:45:39
Message-ID: CACrcyfKtoMmgzVW=6m9t6xKc5UcyZ_673QawSOWC9ZAUZJ8i+Q () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


That is in the write() and read() api calls.

Check the offset values

There are no "seek" io call, it if just a index pointer internally in the
kernel (at least how I understand it)

Regards Tomas

Den tis 10 dec. 2019 kl 21:08 skrev Leah Rumancik <ler13f@my.fsu.edu>:

> I am working on a FUSE file system which stores the content of multiple
> files as a single file. I saw that lseek was recently added for FUSE but
> only for the SEEK_DATA and SEEK_HOLE flags. It would be beneficial for my
> system to be able to modify lseek for the other flags (SEEK_SET, SEEK_END,
> SEEK_CUR). Where in FUSE are the lseek calls with SEEK_SET, SEEK_END, and
> SEEK_CUR filtered out (to be passed to the underlying file system instead
> of going through FUSE)? Thanks!
> --
> fuse-devel mailing list
> To unsubscribe or subscribe, visit
> https://lists.sourceforge.net/lists/listinfo/fuse-devel
>

[Attachment #5 (text/html)]

<div dir="ltr"><div>That is in the write() and read() api \
calls.</div><div><br></div><div>Check the offset \
values</div><div><br></div><div>There are no &quot;seek&quot; io call, it if just a \
index pointer internally in the kernel (at least how I understand \
it)</div><div><br></div><div>Regards Tomas<br></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">Den tis 10 dec. 2019 kl 21:08 \
skrev Leah Rumancik &lt;<a \
href="mailto:ler13f@my.fsu.edu">ler13f@my.fsu.edu</a>&gt;:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">




<div dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
 I am working on a FUSE file system which stores the content of multiple files as a \
single file. I saw that lseek was recently added for FUSE but only for the SEEK_DATA \
and SEEK_HOLE flags. It would be beneficial for my system to be able to modify lseek \
for  the other flags (SEEK_SET, SEEK_END, SEEK_CUR). Where in FUSE are the lseek \
calls with SEEK_SET, SEEK_END, and SEEK_CUR filtered out (to be passed to the \
underlying file system instead of going through FUSE)? Thanks!</div> </div>

-- <br>
fuse-devel mailing list<br>
To unsubscribe or subscribe, visit <a \
href="https://lists.sourceforge.net/lists/listinfo/fuse-devel" rel="noreferrer" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/fuse-devel</a><br> \
</blockquote></div>





-- 
fuse-devel mailing list
To unsubscribe or subscribe, visit https://lists.sourceforge.net/lists/listinfo/fuse-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic