Renamed size_limit -> file_limit
This limits the maximum size of a file, which is also implies the maximum integer size required to mount. The exact name is a bit of a toss-up. I originally went with size_limit to avoid confusion around if file_limit reflected the file size or the number of files, but since this ends up mapping to lfs_off_t and _not_ lfs_size_t, I think size_limit may be a bit of a bad choice.
This commit is contained in:
@@ -249,7 +249,7 @@ struct lfs_config {
|
||||
// Optional upper limit on files in bytes. No downside for larger files
|
||||
// but must be <= LFS_FILE_MAX. Defaults to LFS_FILE_MAX when zero. Stored
|
||||
// in superblock and must be respected by other littlefs drivers.
|
||||
lfs_size_t size_limit;
|
||||
lfs_size_t file_limit;
|
||||
|
||||
// TODO document
|
||||
lfs_size_t uattr_limit;
|
||||
@@ -588,7 +588,7 @@ typedef struct lfs {
|
||||
|
||||
const struct lfs_config *cfg;
|
||||
lfs_size_t name_limit;
|
||||
lfs_off_t size_limit;
|
||||
lfs_off_t file_limit;
|
||||
lfs_size_t uattr_limit;
|
||||
lfs_size_t sattr_limit;
|
||||
|
||||
|
||||
Reference in New Issue
Block a user