RetroSearch Browse

Mon Jan 9 14:02:53 CET 2012 · https://mail.python.org/pipermail/python-dev/2012-January/115421.html

2012/1/9 Charles-François Natali <neologix at free.fr>:
>>> Can rewinddir() end up touching the filesystem to retrieve data? I
>>> noticed that your previous change (the one this checkin reverted)
>>> moved it outside the GIL release macros.
>>
>> It just resets a position count. (in glibc).
>
> Actually, it also calls lseek() on the directory FD:
> http://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/rewinddir.c;hb=HEAD
>
> But lseek() doesn't (normally) perform I/O, it just sets an offset in
> the kernel file structure:
> http://lxr.free-electrons.com/source/fs/read_write.c#L38

Sorry, I should have implied I looked at the kernel source, too. :)

-- 
Regards,
Benjamin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-January/115421.html below:

[Python-Dev] [Python-checkins] cpython: Backed out changeset 36f2e236c601: For some reason, rewinddir() doesn't work as